Skip to main content
Glama

Read Recipe Build Research

get_recipe_build_research
Read-onlyIdempotent

Read the research policy, tier, and recorded evidence 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": "get_recipe_build_research"
  }
}

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 covered. The description adds only content scope (policy, tier, recorded evidence) and says nothing about access requirements for a 'private' build or what happens when no research has been recorded yet.

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 tight sentence with the scope constraint front-loaded and no filler. It is appropriately sized for a one-parameter read tool, though the brevity comes at the cost of any routing or parameter detail.

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 structurally simple (one required parameter, read-only). Still missing is any hint about build_ref format and how the tool behaves for a build with no recorded research, which matters for a tool explicitly about 'recorded evidence'.

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?

The single parameter build_ref has 0% schema description coverage, so the schema supplies only a name, type and length bounds. The description contributes only 'one private build', which implies the ref identifies a build but gives no format, source, or example of what a valid build_ref looks like.

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 uses a specific verb ('Read') plus a concrete resource set ('research policy, tier, and recorded evidence') scoped to 'one private build'. That is enough to separate it from the write-side siblings like record_recipe_research and commit_recipe_research_upload, though the distinction is implied by the verb 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 Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The phrase 'for one private build' scopes the call but does not tell an agent under what circumstances to reach for this tool versus record_recipe_research or get_recipe_build.

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