Skip to main content
Glama

Read Recipe Build Contracts

get_recipe_build_contracts
Read-onlyIdempotent

Read the declared input and output contracts of 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_contracts"
  }
}

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 a closed-world scope, so safety behavior is covered. The description contributes the meaningful qualifier 'declared' (the authored contract rather than any resolved/effective form) and 'private build', but says nothing about what happens when no contracts are declared or when the build ref is unknown.

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?

One sentence, zero filler, with the scope restriction ('one private build') front-loaded. It is efficient, though its brevity leaves gaps that other dimensions penalize.

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, and the tool is low complexity with one required parameter. Still, with the only parameter undocumented and no guidance on selecting this tool over get_recipe_build_schemas or set_recipe_contracts, the definition is only minimally sufficient.

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 parameter build_ref, so the schema supplies only a string with length bounds. The description implies build_ref identifies 'one private build' but adds no format, provenance, or scope detail to help construct a valid reference.

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 ('Read') and a specific resource ('declared input and output contracts of one private build'), which is enough to separate it from the write-side sibling set_recipe_contracts. It stops short of naming or distinguishing get_recipe_build_schemas, which an agent could plausibly confuse with 'contracts'.

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 when-to-use guidance, no exclusions, and no named alternative. The only usage signal is the implied pairing with set_recipe_contracts that the agent must infer from the word 'declared'.

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