Skip to main content
Glama

context_budget_verify

Verify an applied context-budget plan to catch missed edits, manual drift, or preserve-span violations and confirm remaining tokens and budget satisfaction.

Instructions

Use after applying a context-budget plan to catch missed edits, manual drift, or preserve-span violations. Input: the planId returned by context_budget_plan. Returns applied and missed finding IDs, violations with file and line ranges, remaining tokens, and satisfied. Do not consider the budget met until satisfied is true.

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": {
      "planId": "<planId>"
    },
    "name": "context_budget_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
planIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden and does disclose the result fields (applied and missed finding IDs, violations with file and line ranges, remaining tokens, satisfied) plus the gating semantics of 'satisfied'. It never states whether verification is read-only or whether it can itself mutate state, leaving that inference to the agent.

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?

Four tight sentences, front-loaded with the usage condition, then input, then return shape, then the gating rule. Nothing repeats the schema or the name, and every sentence carries distinct information.

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

Completeness5/5

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

For a one-parameter verification tool with no output schema and no annotations, the description supplies the missing return contract and the success condition. An agent has enough to decide when to call it and how to interpret the result.

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

Parameters4/5

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

Schema coverage is 0% for the single planId parameter, but the description compensates by stating its provenance: it is the planId returned by context_budget_plan. That provenance is the key semantic an agent needs and is absent from the schema itself.

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

Purpose5/5

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

States a specific verb and resource: verifying an applied context-budget plan to catch missed edits, manual drift, and preserve-span violations. It is clearly distinguishable from siblings because it operates on a planId produced by context_budget_plan rather than planning or measuring.

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

Usage Guidelines4/5

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

Explicitly says to use it 'after applying a context-budget plan', which pins down the lifecycle position, and adds a hard decision rule: don't consider the budget met until satisfied is true. It does not name when-not to use it or point at an alternative sibling, so it falls short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.