PROBLEM — There is no way today to get a ready-made briefing for how to connect to and work with one specific agent instance over MCP. A caller starting a fresh Claude or Codex session against a known instance has to rediscover, by trial and error, which tools that instance exposes, the exact tool and field names (list_instance_tools then call_instance_tool), and any instance-specific conventions. This session hit exactly that: repeated guessed tool names and guessed field names before landing on the right call shape.
CHECKED AND CONFIRMED MISSING — get_instance_instructions exists but returned an empty string for this instance (a185b1db-c560-456d-9522-f7792bd95cca) — it appears to hold a free-form custom instructions field, not a generated guide, and it is unset here. get_instance_operator_manual exists but the call did not complete. Neither is confirmed to already deliver the capability described below; if either turns out to already be intended for this, the fix may be to populate/generate it rather than add something new — please check the existing intent of both before building new plumbing.
PROPOSAL — A generated, per-instance connection guide containing: the instance id, its agent type, its registered repo (if any), the tools it actually exposes (from list_instance_tools), the exact call_instance_tool shape with real examples using its real tool names and field names, and any instance-specific operating notes. This should be:
- Available as an MCP tool a caller can invoke to fetch that instance's guide as plain text, suitable for pasting directly into another assistant's system instructions.
- Surfaced in the console UI on the instance's own page, with a copy button, so a human can grab it without going through MCP at all.
GOAL — Eliminate the discover-by-guessing loop for a caller who already knows which instance they are targeting, by giving them the exact contract up front instead of deriving it through failed calls.
RELATED — Distinct from #771 (direct per-agent-type tool exposure, which removes the discovery hop programmatically). This issue is about producing a human/assistant-readable reference for the existing discovery contract, useful even if #771 is never built.
PROBLEM — There is no way today to get a ready-made briefing for how to connect to and work with one specific agent instance over MCP. A caller starting a fresh Claude or Codex session against a known instance has to rediscover, by trial and error, which tools that instance exposes, the exact tool and field names (list_instance_tools then call_instance_tool), and any instance-specific conventions. This session hit exactly that: repeated guessed tool names and guessed field names before landing on the right call shape.
CHECKED AND CONFIRMED MISSING — get_instance_instructions exists but returned an empty string for this instance (a185b1db-c560-456d-9522-f7792bd95cca) — it appears to hold a free-form custom instructions field, not a generated guide, and it is unset here. get_instance_operator_manual exists but the call did not complete. Neither is confirmed to already deliver the capability described below; if either turns out to already be intended for this, the fix may be to populate/generate it rather than add something new — please check the existing intent of both before building new plumbing.
PROPOSAL — A generated, per-instance connection guide containing: the instance id, its agent type, its registered repo (if any), the tools it actually exposes (from list_instance_tools), the exact call_instance_tool shape with real examples using its real tool names and field names, and any instance-specific operating notes. This should be:
GOAL — Eliminate the discover-by-guessing loop for a caller who already knows which instance they are targeting, by giving them the exact contract up front instead of deriving it through failed calls.
RELATED — Distinct from #771 (direct per-agent-type tool exposure, which removes the discovery hop programmatically). This issue is about producing a human/assistant-readable reference for the existing discovery contract, useful even if #771 is never built.