TeamShared

agent_run_child

Run a nested Cloud Agent to completion; returns summary and artifact refs only.

Only available inside an active TeamShared Cloud Agent run. The child's transcript is not appended to this run's message history.

Input Schema

Name	Required	Description
`repo`	No	Optional workspace slug
`agent`	No	Override agent attribution label
`brief`	Yes	Isolated goal and constraints for the nested worker
`model`	No	Optional router model id
`tools`	No	Tool patterns for the child; cannot widen this run's allowlist
`github`	No	Optional owner/repo checkout; defaults to this run's repo. An explicit, inherited, or code-tagged org-default slug the App does not serve is refused (github_repo_not_bound). A failed installation read refuses a named slug (github_binding_unavailable)
`durable_memory`	No	Keep the child's own capture session and run memory, for a specialist that must remember its work. Default false.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

changedInput schema / properties / github / description

Previous value: -"Optional owner/repo checkout; defaults to this run's repo"New value: +"Optional owner/repo checkout; defaults to this run's repo. An explicit, inherited, or code-tagged org-default slug the App does not serve is refused (github_repo_not_bound). A failed installation read refuses a named slug (github_binding_unavailable)"

AddedOct 19, 2026
RemovedSep 25, 2026

Changed1 schema field changedSep 25, 2026

addedInput schema / properties / durable_memory

Added value: +{
+  "default": false,
+  "description": "Keep the child's own capture session and run memory, for a specialist that must remember its work. Default false.",
+  "type": "boolean"
+}

AddedSep 24, 2026

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and usefully discloses that only summary and artifact refs are returned and that the child transcript is not appended to this run's history. However, it omits operational behavior such as credit consumption, failure handling, concurrency limits, and whether the call is blocking beyond the phrase 'to completion'.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three short sentences and front-loads the core action. Every sentence adds relevant information: the operation, the restricted availability, and the transcript isolation behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema exists, so return values need not be explained in detail, and the input schema covers parameters richly. The description supplies the key non-obvious context about nested execution and transcript isolation, though it leaves out some operational details like credit impact and failure modes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the input schema already documents all seven parameters thoroughly. The description adds no parameter-specific meaning beyond what the schema provides, which is the baseline expectation when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: run a nested Cloud Agent to completion. It explicitly distinguishes this from top-level run tools by saying it is only available inside an active TeamShared Cloud Agent run and returns only summary and artifact refs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a clear precondition, that it only works inside an active TeamShared Cloud Agent run, but it does not contrast this with alternatives such as agent_run_start or agent_run_followup. The usage is implied rather than explicitly routed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TeamShared tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.