Skip to main content
Glama

SCRIPTMASTERLABS — Provider Trust + CANON

Check History

check_history
Read-onlyIdempotent

Check recent evidence-backed provider history. Traffic volume is context only and is never presented as buyers, trust, or reputation.

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

Input Schema

NameRequiredDescriptionDefault
hoursNoHistorical lookback window in hours (1-2160; default 720, i.e. 30 days) over which evidence-backed provider history is summarized.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / hours / description
      Added value: +"Historical lookback window in hours (1-2160; default 720, i.e. 30 days) over which evidence-backed provider history is summarized."
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description does add real value beyond them by warning that traffic volume is context only and must not be read as buyers, trust, or reputation, which shapes how the output should be interpreted. It still omits what the history records contain and how results are shaped.

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?

Two sentences, zero filler, with the purpose front-loaded and the interpretive caveat second. The only weakness is that the opening sentence leans on unexplained jargon ("evidence-backed") rather than concrete nouns.

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

Completeness3/5

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

With one optional parameter, no output schema, and annotations covering the safety profile, the bar is modest, and the description meets it for interpretation guidance. It falls short of full completeness because an agent still cannot predict what a "history" result contains or why one would choose this over the other check_* tools.

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% and the single hours parameter is fully documented with range, default, and meaning in the schema. The description adds nothing about the lookback window or how the window affects the summary, so the baseline 3 applies.

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

Purpose3/5

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

The description gives a verb plus a resource ("Check recent evidence-backed provider history"), so the general aim is legible. However, "evidence-backed" and "history" are undefined, and nothing distinguishes this from siblings such as check_identity, check_status, or verify_provider, so an agent must open the schema to learn what is actually returned.

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?

There is no statement of when to call this instead of check_identity, verify_provider, or compare_providers, and no prerequisites or exclusions are given. The only usage-adjacent content is a caution about interpreting results, not about choosing the tool.

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