Skip to main content
Glama

Rehearse defense

rehearse_defense

$1 bounded policy rehearsal. Returns a model and local hash measurement.

Does not activate endpoint protection or establish energy savings.

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": {
      "client_hashes_per_second": "<client_hashes_per_second>",
      "client_p95_budget_ms": "<client_p95_budget_ms>",
      "backend_cost_ms": "<backend_cost_ms>",
      "peak_requests_per_second": "<peak_requests_per_second>"
    },
    "name": "rehearse_defense"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idNoOptional. Your id for this call. Repeat it to retry safely: the same request_id is never charged twice.
payment_refNoOptional. A paid credit or payment reference, used only after the free daily calls. Leave it out to use the free tier or a seat.
backend_cost_msYesBackend time per request in milliseconds.
client_p95_budget_msYesMost extra latency, in milliseconds, clients may pay at the 95th percentile.
client_hashes_per_secondYesHashes per second a typical client device can compute.
peak_requests_per_secondYesExpected peak request rate.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / backend_cost_ms / description
      Added value: +"Backend time per request in milliseconds."
    • addedInput schema / properties / client_hashes_per_second / description
      Added value: +"Hashes per second a typical client device can compute."
    • addedInput schema / properties / client_p95_budget_ms / description
      Added value: +"Most extra latency, in milliseconds, clients may pay at the 95th percentile."
    • addedInput schema / properties / payment_ref / description
      Added value: +"Optional. A paid credit or payment reference, used only after the free daily calls. Leave it out to use the free tier or a seat."
    • addedInput schema / properties / peak_requests_per_second / description
      Added value: +"Expected peak request rate."
    • addedInput schema / properties / request_id / description
      Added value: +"Optional. Your id for this call. Repeat it to retry safely: the same request_id is never charged twice."
  2. Changed2 schema fields changed
    • addedInput schema / properties / payment_ref
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Payment Ref"
      +}
    • addedInput schema / properties / request_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Request Id"
      +}
  3. First observed

TDQS

C2.4/5.0
Behavior3/5

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

The description adds genuinely useful negative disclosure: it does not activate endpoint protection or establish energy savings, and it costs $1. That goes beyond the annotations. However, it says nothing about the non-idempotent, non-read-only behavior the annotations imply (what state "rehearsal" touches) or what the returned model contains.

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?

Three short front-loaded sentences with no padding, which is commendable. But the brevity crosses into opacity: the lead clause is too compressed to convey meaning, so the terseness costs clarity rather than buying it.

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?

An output schema exists so return values need not be explained, but for a 6-parameter priced operation the description omits what is being simulated and under what conditions, leaving the agent unable to judge applicability. The negative-effect sentences are the only substantive content.

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 coverage is 100% and every parameter carries its own description, so the schema does the heavy lifting. The description adds no meaning about how the four required inputs (hash rate, latency budget, backend cost, peak RPS) combine into the result, so baseline 3 applies.

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

Purpose2/5

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

"Bounded policy rehearsal" largely restates the title "Rehearse defense" in jargon and never says what is actually simulated or computed. It hints at outputs ("a model and local hash measurement") but an agent cannot tell what the operation is for or how it differs from describe_agent.

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?

No when-to-use or when-not-to-use guidance, and the only sibling, describe_agent, is neither referenced nor distinguished. The bare "$1" implies a cost gate but gives no context for choosing this tool over alternatives.

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.