Skip to main content
Glama

List Recipe Build Nodes

list_recipe_build_nodes
Read-onlyIdempotent

List node identifiers and node types in 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_nodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
build_refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so safety is covered. The description adds only the 'private build' scoping, which hints that access is limited to builds the caller owns; it says nothing about ordering, pagination, or what happens for a nonexistent or non-private build_ref.

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 front-loaded sentence with no filler; the key scope ('one private build') arrives immediately. Nothing is wasted, though nothing is elaborated either.

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 and the annotations are rich, so the return shape and safety profile need not be repeated. Still, for a one-parameter list tool in a dense cluster of similarly named siblings, the definition leaves the agent guessing about pagination and about which sibling to pick.

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 coverage is 0% for the single build_ref parameter, but the description's 'in one private build' does establish that build_ref selects exactly one build rather than aggregating across builds. It adds no format, ID convention, or error semantics beyond that.

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 states a specific verb ('List') and resource ('node identifiers and node types') scoped to 'one private build', so the operation is unambiguous. It does not, however, differentiate itself from close siblings such as get_recipe_build_node or list_recipe_build_activities.

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?

There is no guidance about when to choose this tool over list_recipe_build_activities, get_recipe_build_node, or the other list_recipe_* siblings, and no stated prerequisites. The agent must infer that this is the shallow index of a build's nodes while get_recipe_build_node fetches one node's detail.

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