Skip to main content
Glama

Read a Recipe Build Node

get_recipe_build_node
Read-onlyIdempotent

Read one node from a private build by its exact node identifier.

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>",
      "node_id": "<node_id>"
    },
    "name": "get_recipe_build_node"
  }
}

Input Schema

NameRequiredDescriptionDefault
node_idYes
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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and determinism are covered structurally. The description adds only that the read targets a 'private build' and requires an exact identifier; it says nothing about failure behavior when the ID is absent or about pagination/size, which is acceptable given the annotation coverage but adds little.

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 front-loaded sentence with zero filler; the scope ('one node') and the keying requirement ('exact node identifier') come first. Nothing is redundant or padding.

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-value explanation is rightly omitted, and annotations cover the safety profile. However, for a two-parameter tool with no schema descriptions, the definition leaves the caller without any guidance on how to obtain a node_id or what a build_ref looks like, which is a meaningful gap for a lookup tool.

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 carries the burden for both parameters. It clarifies node_id as an 'exact node identifier', but build_ref is left entirely unexplained — the schema gives only a 1..4096 character string, with no hint whether it is a name, ID, or path. A caller still cannot tell what to put in build_ref.

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 names a specific verb and resource ('Read one node from a private build') and scopes it to a single item by exact identifier, which separates it from list_recipe_build_nodes and the aggregate get_recipe_build. It stops short of naming any sibling explicitly, so the differentiation is inferred rather than stated.

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?

The phrase 'by its exact node identifier' implies a prerequisite (you must already hold a node ID, so this is a lookup, not a discovery call), which is useful implied guidance. There is no explicit statement of when to prefer this over list_recipe_build_nodes or get_recipe_build, and no exclusions.

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