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.

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.8/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive semantics, and the description adds real context beyond that: the daily cadence, one fixed prompt per model, the exact verdict vocabulary, the returned time-of-last-check and unchanged-duration fields, and that authentication is not required. It does not discuss rate limits or failure handling.

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?

Front-loaded with the purpose, then the mechanism, verdict set, and provenance. The first sentence is a dense run-on enumerating four verdict values, but every clause carries information; the short second and third sentences are efficient.

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?

With no output schema and a single optional parameter, the description supplies what an agent needs: what is measured, the possible verdicts, the auxiliary return fields, the update cadence, and the underlying data source. Nothing material is missing for correct invocation.

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 parameter is fully described in the schema (100% coverage, default = every model), so the schema carries the weight. The description only indirectly touches filtering by saying the prompt goes to "every model," which does not fully explain the optional single-model narrowing.

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 the daily fixed-prompt mechanism identifies a concrete resource (per-model identity/drift status) and output shape (stable/changed/failed/unchecked). It is clearly not a chat, generate, or list tool, though it never names a sibling to contrast against.

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 only implied: an agent can infer this is for verifying model identity over time. There is no explicit when-to-use statement, no when-not-to-use exclusion, and no routing to an alternative sibling such as list_models.

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.