Skip to main content
Glama

Read Recipe Build Schemas

get_recipe_build_schemas
Read-onlyIdempotent

Read the named JSON schemas stored 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": "get_recipe_build_schemas"
  }
}

Input Schema

NameRequiredDescriptionDefault
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 openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds the useful scoping fact that schemas live inside a single private build, but says nothing about volume, ordering, or what happens when a build has no schemas. Given the annotation coverage, a 3 reflects modest added value.

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, and the scoping constraint is placed immediately. It is efficient, though its brevity tips into under-specification rather than tight completeness.

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 one-parameter read tool the description is close to sufficient, but it leaves unresolved whether all named schemas are returned or a subset, and how to obtain a valid build_ref. Minimum viable rather than 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% for the single required parameter build_ref, so the description must carry the burden. It only obliquely implies the parameter by saying 'one private build', giving no format, source, or example for a build reference. That is insufficient for an agent to construct a valid value without consulting other tools.

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+resource: read JSON schemas that belong to a single private build. The resource noun 'schemas' separates it from siblings such as get_recipe_build_contracts or get_recipe_build_node without needing to name them. It stops short of 5 because 'the named JSON schemas' is ambiguous given there is no name parameter in the schema.

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?

No when-to-use or when-not-to-use guidance, and no alternative is mentioned. An agent must infer from the name alone whether this is the right call versus get_recipe_build or get_recipe_build_contracts. The only implicit signal is the word 'private', which hints at scoping but not at selection.

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