Server definition
- Hash
- sha256:f6eae5f73deacdb4cdfd9060a6f9c29d3f4ae9b1d1afe60e7d793b8eb70edb77
- What it is
- What a remote MCP server returned when asked what it offers: 4 tools
The blob, as servednamed by its sha256
{
"instructions": "This connection reports into a space the user opened to watch the work done in this\nproject from anywhere. Report everything you do here without being asked: every turn\nthat does any work gets a task, reading and answering included.\n\n- create_task when the work starts, and one child per step with parent_uuid.\n- update_task as each step moves, and complete_task as each step ends, not in a sweep\n at the end. A board that stays empty until the job is over tells the user nothing.\n- complete_task the parent last. Completing is what sends the user a notification, so\n complete work that failed too, with the failure in values.\n",
"tools": [
{
"description": "Mark a task finished. This is what sends the user's push notification, so call\nit when the work is actually done — including when it failed, with the failure\nrecorded in values.\n\nCall it as part of the step that finishes the work, not in a sweep once\neverything is done. Closing a whole tree at the end is cheaper for you and\nleaves the user watching an empty board for the entire job.\n\nNothing finishes a parent for you: complete it once its last step is done.\nCompleting a parent also stops every step under it that is still open, so a job\nthat ends early is closed by completing the parent alone. Those steps show as\nstopped, not done, with their numbers as they were.\n",
"inputSchema": {
"properties": {
"task_uuid": {
"description": "The uuid returned by create_task.",
"type": "string"
},
"values": {
"description": "Final numbers or a closing log line, e.g. {\"status\": \"failed\", \"log\": \"exit 1\"}. Same limits as update_task.",
"maxProperties": 20,
"type": "object"
}
},
"required": [
"task_uuid"
],
"type": "object"
},
"name": "complete_task",
"outputSchema": null
},
{
"description": "Create a space — the container tasks live in, and what the user opens to watch\nthem.\n\nOnly call this when no space is configured for this connection and creating a\ntask failed for that reason. If a space is already configured, use it: making a\nsecond one splits the user's tasks across two screens they have to add\nseparately.\n\nReturns the space uuid and the URL to watch it. Give the user that URL — until\nthey open it, nothing you report is visible to them, and the uuid is the only\nway back to it.\n",
"inputSchema": {
"properties": {
"icon": {
"description": "One character shown beside the name. An emoji reads best, e.g. \"🌙\".",
"type": "string"
},
"title": {
"description": "What this collection of tasks is for, e.g. \"Nightly builds\". At most 100 characters; longer is cut to 100, the last one an ellipsis.",
"maxLength": 100,
"type": "string"
}
},
"required": [
"title"
],
"type": "object"
},
"name": "create_space",
"outputSchema": null
},
{
"description": "Create a task the user can watch from anywhere while it runs.\n\nCall this first in every turn you do any work, reading and answering included,\nwithout being asked and however small the work looks: the user connected this\nserver to watch exactly that work, and a turn that reports nothing looks to them\nlike a turn that never happened. Returns a task uuid to report against.\n\nIf you decompose work into steps, create one child task per step by passing\nparent_uuid. Nesting is one level only: a child cannot have children. A parent's\nprogress is averaged from its children automatically, so never report progress\non a parent yourself.\n\nCreate the whole tree before starting, then report each step as it happens and\ncomplete it when it is actually done — not all of them at the end. A board that\nstays empty for the whole job and turns green at the finish is worth nothing to\nwhoever is watching it.\n\nKeep creating steps as work appears. The tree is a live picture, not a plan you\nfixed at the start: something you did not foresee gets its own step when you\nfind it, rather than being folded into whichever step is already open. A parent\nwhose bar drops because it gained a step is telling the truth.\n",
"inputSchema": {
"properties": {
"parent_uuid": {
"description": "Make this a step of an existing task. One level only.",
"type": "string"
},
"source": {
"description": "What is reporting, e.g. the agent or tool name. At most 100 characters; longer is cut to 100, the last one an ellipsis.",
"maxLength": 100,
"type": "string"
},
"space_uuid": {
"description": "Only needed to override the space configured for this connection.",
"type": "string"
},
"title": {
"description": "What this task is doing, in a few words. At most 200 characters; longer is cut to 200, the last one an ellipsis.",
"maxLength": 200,
"type": "string"
}
},
"required": [
"title"
],
"type": "object"
},
"name": "create_task",
"outputSchema": null
},
{
"description": "Report progress on a task. Call periodically — every meaningful step, not every\nloop iteration.\n\nCall it once when the work actually begins, too. A task that has been created but\nnever reported reads as \"waiting for data\", which nobody can tell apart from a\nreporter that died before its first write. If the step has nothing to count, send\ncurrent 0 and end 1: that reads as running, and it is honest.\n\n`current` and `end` are raw counts, not a percentage: the user sees\n\"1200 of 50000 pages\", which tells them something \"2.4%\" does not. `end` may\nchange as you learn more; send the new number and the bar recalculates.\n\nEvery call replaces the whole state. Send everything each time — anything you\nleave out is cleared, not kept. Put a one-line status in values.log; it holds\nthe last line only, not a history.\n\nA task uuid is all this needs — it already knows which space it belongs to.\n",
"inputSchema": {
"properties": {
"current": {
"description": "How much is done so far.",
"type": "number"
},
"end": {
"description": "How much there is in total.",
"type": "number"
},
"task_uuid": {
"description": "The uuid returned by create_task.",
"type": "string"
},
"values": {
"description": "Flat object of extra numbers or strings, e.g. {\"errors\": 3, \"log\": \"retrying /foo\"}. At most 20 keys of at most 40 characters, or the request is refused with 400. A string is cut to 1000 characters, the last one an ellipsis.",
"maxProperties": 20,
"type": "object"
}
},
"required": [
"task_uuid"
],
"type": "object"
},
"name": "update_task",
"outputSchema": null
}
]
}Verify it yourself
curl -s https://api.teppi.xyz/v1/evidence/sha256:f6eae5f73deacdb4cdfd9060a6f9c29d3f4ae9b1d1afe60e7d793b8eb70edb77 | sha256sum