harness_describe
Writes a manifest for the connected harness when identity reports an unknown runtime, capturing tool surface, sandbox, delegation, scheduling, memory layers, and gotchas.
Instructions
Self-describe the CURRENTLY CONNECTED harness: write its manifest at /harnesses/.md (see stack spec v1 §4.7). Call this when identity() reports an onboarding block for an unknown runtime. The target is derived from your own MCP clientInfo.name — you can only describe yourself, not another harness. Re-runnable: overwrites the manifest each time. The body should cover: tool surface / prefixes, sandbox & filesystem, delegation primitive, scheduling, session search, memory layers, and gotchas.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"content": "<content>"
},
"name": "harness_describe"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| content | Yes | The manifest body (markdown). Frontmatter is stamped automatically. | |
| version | No | Manifest version stamp (default "0.1"). |