Skip to main content
Glama

List Recipe Build Capabilities

list_recipe_build_capabilities
Read-onlyIdempotent

Page through the supported authoring capabilities 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_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
cursorNo
build_refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is fully covered. The description adds that results are paginated and restricted to supported capabilities of a private build, but says nothing about page sizing, termination, or what an empty page implies.

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?

A single well-formed sentence with the resource and the scoping constraint front-loaded. Nothing is redundant, but the terseness leaves obvious information out rather than trimming waste.

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 return values need not be explained. For a paginated read over a build sub-resource the definition is minimally sufficient, but 'capability' and 'supported' are never grounded, leaving the agent to infer what is actually listed.

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%, so the description must carry the three parameters. 'Page through' hints at cursor/limit and 'one private build' hints at build_ref, but there are no details on the identifier format, the limit ceiling of 25, or the maximum cursor length.

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-plus-resource ("page through the supported authoring capabilities") scoped to one private build. That scope distinguishes it from the global sibling list_recipe_capability_types, though it does not name that sibling explicitly.

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

Usage Guidelines2/5

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

The only usage signal is the implied 'inspect a build's capabilities' context. There is no statement of when to use this versus listing capability types or inspecting build nodes/activities, and no prerequisites mentioned.

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