Skip to main content
Glama

Read a Recipe Acceptance Plan

get_recipe_acceptance_plan
Read-onlyIdempotent

Read or page through the behavioral acceptance plan 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_acceptance_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNo
build_refYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/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. The description adds the useful constraint that the plan is scoped to a single private build and that results are paged, but says nothing about what the plan contains or how large it typically is. With annotations carrying the behavioral load, this is adequate but not rich.

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 sentence with zero filler, front-loading both the action and the resource. Nothing is repeated from the title or schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 read-only annotations cover the safety contract. For a two-parameter read tool this is close to sufficient; only the vague notion of a "behavioral acceptance plan" and the lack of any alternative-tool routing keep it from being complete.

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 description coverage is 0%, so the description must compensate for both parameters. "Page through" implicitly maps to the cursor parameter and "one private build" maps to build_ref, which is partial compensation, but no format, token semantics, or paging termination behavior is given.

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 ("Read or page through") and a specific resource ("the behavioral acceptance plan"), scoped to "one private build." It is clear enough to distinguish reading the plan from sibling mutation tools like set_recipe_acceptance_cases, but it does not explicitly separate itself from quote_recipe_acceptance or run_recipe_acceptance.

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 stated when-to-use guidance, no prerequisites, and no mention of alternatives such as quoting or running the acceptance plan. Usage is only implied by the verb "Read," leaving the agent to infer the selection criteria itself.

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