Skip to main content
Glama

Quote Recipe Acceptance

quote_recipe_acceptance
Idempotent

Quote selected or complete behavioral acceptance cases without starting them.

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>"
    },
    "name": "quote_recipe_acceptance"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_idsNo
revisionYes
build_refYes
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare that the tool is not read-only, is idempotent, and is non-destructive. The description adds useful context that it does not start the cases, but it does not explain what 'quote' creates or returns, or why idempotency_key is required for this operation.

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?

The description is a single front-loaded sentence with no redundant wording. Every phrase contributes to scope or usage.

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?

For a tool with three required parameters and no schema descriptions, the definition is too thin to guide correct invocation. The output schema and annotations cover some return and safety context, but the description leaves the meaning of the required build/revision/idempotency inputs unexplained.

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%, so the description must compensate for four undocumented parameters. It only clarifies that case_ids can represent selected cases versus complete coverage when omitted; it says nothing about build_ref, revision, or idempotency_key.

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 states a specific verb and resource: quote behavioral acceptance cases, either selected or complete. It also adds the key scope constraint 'without starting them,' which helps distinguish it from run_recipe_acceptance, though it does not explicitly differentiate from quote_recipe_review.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The phrase 'without starting them' implies a when-to-use condition: use this when a quote is wanted but execution should not begin. However, it does not name alternatives such as run_recipe_acceptance or quote_recipe_review, nor does it state explicit exclusions or prerequisites.

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