Skip to main content
Glama

Daily real-model check

proof
Read-onlyIdempotent

Whether each model is still the model it says it is: every day one fixed prompt goes to every model and the verdict per model is stable, changed, failed or unchecked, with the time of the last check and how long the answer has been unchanged. No key needed. Live from GET /v1/proof; method at https://uplinkswitch.ai/proof/method.

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": "proof"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoOne model id. Default: every model.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (which already cover read-only, idempotent, non-destructive, closed-world), the description discloses the daily cadence, the fixed-prompt method, the exact verdict vocabulary, the freshness fields returned, that no API key is required, and a method link. Only the response envelope shape is left unstated, so this is a strong value-add over structured fields.

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 core behaviour is front-loaded and the supporting facts (no key, endpoint, method URL) are compact. The opening clause is a slightly convoluted way to say "per-model integrity status", costing a little parsing effort, but nothing is padded or redundant.

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 one-optional-parameter, read-only status tool with no output schema, the description explains what the returned verdicts mean, what freshness data accompanies them, and that no auth is needed. The only real omission is the shape of the response object versus a list, which is minor at this complexity.

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?

The single `model` parameter is already fully documented in the schema ("One model id. Default: every model."), and the description never mentions it, adding no narrowing semantics or id-format hints. With 100% schema coverage and one optional param, the baseline 3 applies.

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

Purpose4/5

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

"Whether each model is still the model it says it is" plus "verdict per model is stable, changed, failed or unchecked" identifies a read-only model-integrity/verification-status tool and enumerates its outcomes. It is clear once parsed, but the opening is indirect (a question rather than a verb+resource) and it never contrasts itself with siblings like list_models or chat.

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

Usage Guidelines3/5

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

Usage is implied by the purpose: consult it to learn whether a model's behaviour has changed since the last daily check. There is no explicit when-to-use/when-not guidance and no named alternative for related questions (e.g. listing available models), so the agent must infer the boundary.

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.