Skip to main content
Glama

List Recipe Build Handoffs

list_recipe_build_handoffs
Read-onlyIdempotent

List supervised acceptance handoffs for one private build.

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": {
      "build_ref": "<build_ref>"
    },
    "name": "list_recipe_build_handoffs"
  }
}

Input Schema

NameRequiredDescriptionDefault
build_refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds essentially no behavior beyond that: no note on pagination, result ordering, permissions needed to see supervised handoffs, or what a 'handoff' state means. With the annotation bar already met, the description contributes minimal extra context.

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

Conciseness4/5

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

One short sentence with the verb and scope front-loaded and no filler. The terseness is efficient, though it borders on under-specification rather than genuine economy.

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

Completeness3/5

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

The tool is simple (one param), annotations are rich, and an output schema exists, so return values need not be explained. Still, domain jargon ('supervised acceptance handoffs', 'private build') is left undefined and the single undocumented parameter is not clarified, leaving the agent to guess at invocation details. Adequate but with clear gaps.

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

Parameters2/5

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

Schema description coverage is 0% for the single required build_ref parameter, so the description must compensate. It only implies that build_ref identifies 'one private build' and gives no format, identifier type, or whether it is a name, ID, or reference path. That is a thin partial compensation for an undocumented parameter.

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

Purpose4/5

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

The description gives a specific verb (List) and resource (supervised acceptance handoffs) scoped to a single private build. The resource noun is distinct from sibling resources such as activities, nodes, capabilities, and resources, so an agent can differentiate it without opening a schema. It stops short of explicitly contrasting with any sibling, which keeps it at 4 rather than 5.

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?

Usage is only implied: the tool lists handoffs for one build, which suggests when it applies, but there is no statement of when to choose it over list_recipe_build_activities or get_recipe_build, and no prerequisites or exclusions. The scoping phrase 'for one private build' is the only routing signal.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources