Skip to main content
Glama

pre_check

Read-onlyIdempotent

Free mechanical pre-check before a paid verification review: given a claims object mapping each criterion key (approvalGates, restartRecovery, evidenceTrail, killSwitch, policyControls, isolation) to a public documentation URL, reports which criteria have documentation linked and which are missing. It checks that links were supplied, never that the documentation proves the claim.

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": {
      "claims": "<claims>"
    },
    "name": "pre_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimsYesMap of criterion key to public documentation URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is low. The description adds real value beyond them: it discloses that the tool is free/mechanical, that it only checks link presence, and explicitly that it does not validate whether documentation proves a claim — an important expectation-setting caveat for an 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?

Two sentences, front-loaded with the purpose and the cost/positioning, followed by the critical limitation. No filler; every clause carries information the agent needs.

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?

With one required parameter, full schema coverage and no output schema, the description covers the input contract, the reported result, and the key behavioral caveat. It does not specify the shape of the report (e.g., per-key booleans vs. a missing-list), which is a minor gap given there is no output schema.

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 description coverage is 100%, including the nested 'Map of criterion key to public documentation URL' description, so the schema already carries the parameter meaning. The description re-enumerates the six criterion keys, which is mildly helpful as confirmation but largely duplicates the schema's property list rather than adding new semantics such as URL format or partial-map behavior.

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 ('reports which criteria have documentation linked and which are missing') plus the scope of the input ('a claims object mapping each criterion key ... to a public documentation URL'). It also positions itself against a sibling concept ('before a paid verification review'), so an agent can tell it apart from the verification step without opening the schema.

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?

The phrase 'Free mechanical pre-check before a paid verification review' gives a clear when-to-use context, and the closing sentence effectively defines when not to rely on it ('never that the documentation proves the claim'). It stops short of naming an explicit alternative tool to call for the content-verification case, which keeps it from a 5.

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