Retrieve the compact YAML-flow grammar reference (commands, selectors, env, switchContext, examples) before writing a flow, with no file lookup needed.
Return the compact YAML-flow grammar reference (commands, selectors, env, switchContext, examples). Call this before authoring a flow — no file lookup needed.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v3.8.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden of behavioral disclosure. It clarifies that this is a reference retrieval with no side effects and is local (no file lookup), which is useful. However, it doesn't describe the return format details or performance characteristics, but since it's a static reference, the key behavioral traits are covered.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences with no redundancy. The purpose is front-loaded and actionable, with the usage hint appended efficiently. Every word contributes value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter reference tool, the description is complete. It specifies the content of the returned reference, when to call it, and that no additional setup is needed. Nothing is missing that an agent would need to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, and the schema coverage is 100% (empty object). The description adds semantic value by indicating what the returned reference contains, which helps the agent understand what to expect. With no parameters, a baseline of 4 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states what the tool returns: a compact YAML-flow grammar reference, listing specific components (commands, selectors, env, switchContext, examples). This is distinct from sibling tools, which are action or query tools rather than reference tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear guidance on when to use this tool: 'Call this before authoring a flow' and notes that no file lookup is needed. This is explicit usage context, though it doesn't mention alternatives or when not to use it, which is acceptable given the tool's unique reference nature.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.