Skip to main content
Glama

Bind a Recipe Acceptance Resource

bind_recipe_resource
Idempotent

Approve one exact frozen resource selector for a supervised acceptance handoff.

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>",
      "revision": "<revision>",
      "idempotency_key": "<idempotency_key>",
      "handoff_ref": "<handoff_ref>",
      "requirement_id": "<requirement_id>"
    },
    "name": "bind_recipe_resource"
  }
}

Input Schema

NameRequiredDescriptionDefault
revisionYes
build_refYes
handoff_refYes
requirement_idYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so safety and idempotency are covered by structured data. The description adds only the vague notions of 'exact' and 'frozen', without saying what the binding pins, what happens if the selector no longer matches, whether re-binding is allowed, or what authorization is required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single front-loaded sentence with no filler, which is structurally clean. The brevity is under-specification rather than efficiency, so it earns only a middling score.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a five-required-parameter mutation with opaque field names and no output-schema need for return values. Given that, the one-sentence description leaves the agent without enough to construct a correct call or understand the binding's effect on the handoff.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across five required parameters whose names (build_ref, revision, handoff_ref, requirement_id, idempotency_key) carry no explanatory text anywhere. The description mentions no parameter at all, so an agent must guess what a 'frozen resource selector' maps to among revision, requirement_id, and build_ref.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Approve' plus the object 'one exact frozen resource selector' gives a partial sense of what the tool does, and 'supervised acceptance handoff' situates it in a workflow. However, the phrasing is abstract jargon, and it never says how this differs from siblings like commit_recipe_acceptance_upload or run_recipe_acceptance, which plausibly act on the same handoff.

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 statement of prerequisites (e.g. an existing handoff_ref), and no mention of alternatives or ordering relative to quote/run/commit acceptance tools. An agent knows only that this is an approval-flavored step, not when to pick it.

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