Skip to main content
Glama

Approve a Recipe Build Budget

approve_recipe_budget
Idempotent

Redeem one exact budget capability for one private build revision.

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

Input Schema

NameRequiredDescriptionDefault
revisionYes
build_refYes
idempotency_keyYes
budget_capabilityYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.3/5.0
Behavior2/5

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

The annotations already indicate this is a non-read-only, idempotent, non-destructive, closed-world operation. The description adds only that redemption is for one exact capability and one private build revision, but it does not explain what redemption does to the budget, what happens if the capability is invalid or expired, or whether the build revision state changes.

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?

The description is a single tightly worded sentence with no filler. However, its extreme brevity is not well matched to a four-required-parameter mutation tool, so the structure is efficient but under-informative.

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 write operation with four required, entirely undocumented parameters and a meaningful approval workflow, the description is incomplete. The output schema and annotations relieve some burden, but the definition still lacks the operational context needed to invoke the tool confidently.

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 carry the burden for four required parameters. It implicitly references a build revision and a budget capability, but says nothing about build_ref, the 64-hex revision format, or idempotency_key semantics, leaving most parameters semantically undocumented.

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 description states a somewhat specific action, redeeming a budget capability for a build revision, but 'redeem' does not clearly match the tool name 'approve' or explain how this differs from sibling budget/capability tools. An agent can infer a mutation involving budget authorization, but the purpose remains abstract.

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

Usage Guidelines1/5

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

The description provides no guidance on when this tool should be used, what prerequisite state a build revision or capability must be in, or when to prefer it over related siblings such as list_recipe_build_capabilities or get_recipe_capability.

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