Skip to main content
Glama

Prepare a request key before checking

prepare_check
Read-only

Generate a fresh request key for one deliberately new check. This does not run a check or reserve capacity. Retain it before dispatch. After an uncertain outcome reuse the original request key and credential; never call this tool to replace an uncertain request.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "prepare_check"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true, idempotentHint=false and destructiveHint=false; the description goes beyond them by clarifying that no check executes and no capacity is reserved, and by prescribing key lifecycle handling after an uncertain outcome. It leaves the key's lifetime and the mechanism for supplying it to the subsequent call unstated, so it stops short of full behavioral disclosure.

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?

Three short sentences, front-loaded with the core action, then the non-behavior, then the retention rule. No filler and no repetition of the title's phrasing beyond what is needed.

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

Completeness4/5

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

For a zero-parameter tool with no output schema, the description covers purpose, side-effect profile, and key-retention protocol. The remaining gap is the return value itself (that a key string is produced and should be retained) and how that key is passed to the follow-up check, which the description only gestures at with "retain it before dispatch."

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline applies. The description correctly conveys that the only input is the intent to start a new check, not any parameter value.

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 ("Generate a fresh request key") and scopes it to "one deliberately new check." It immediately bounds the purpose negatively ("does not run a check or reserve capacity"), which separates it from check_asset without needing to name it.

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

Usage Guidelines5/5

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

Gives explicit when-to-use (a deliberately new check) and an explicit when-not-to-use (never to replace an uncertain request), plus the alternative behavior to follow instead (reuse the original key and credential). This is the full when/when-not/alternative triad.

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