Skip to main content
Glama

List Recipe Build Resources

list_recipe_build_resources
Read-onlyIdempotent

List resource requirements from the newest handoff 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_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
build_refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description is not required to carry it. The one genuinely additive detail is that the tool reads from the *newest* handoff, i.e. it implicitly selects a handoff rather than letting the caller choose one. It does not say what happens when no handoff exists or whether older handoffs are ever considered, which is the kind of context that would push this higher.

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?

A single sentence with the scope and source front-loaded and no filler wording. Every clause (resource requirements, newest handoff, one private build) carries information an agent needs.

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?

An output schema exists, so the return shape need not be described, and annotations cover safety, which lowers the burden. What remains unaddressed is how to supply build_ref and how the tool behaves when the build has no handoff yet. Adequate for a narrow single-parameter read, but not complete.

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%: build_ref is typed as a bounded string with no explanation of what identifier it expects or where to obtain it. The phrase 'one private build' faintly maps build_ref to a single build identifier, but the description adds no format, provenance, or error behavior for the only parameter. That is thin compensation for a complete schema gap.

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?

States a specific verb and resource: 'List resource requirements', scoped to 'the newest handoff for one private build'. This is materially distinct from the sibling list_recipe_build_handoffs, which enumerates handoffs rather than reading requirements out of one. It stops short of naming a sibling or stating the distinction explicitly, so it lands 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 implied by the scope phrase: call this when you need the resource requirements for a single private build. There is no explicit when-to-use framing, no when-not to use it, and no pointer to an alternative for related needs such as listing handoffs or capabilities. An agent must infer the selection criteria.

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