Skip to main content
Glama

Publication evidence freshness

bpj_claim_evidence_checklist
Read-onlyIdempotent

Review logged sources for stale or future-dated checks against a supplied review date and freshness window.

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>",
      "asOf": "<asOf>",
      "maxAgeDays": "<maxAgeDays>"
    },
    "name": "bpj_claim_evidence_checklist"
  }
}

Input Schema

NameRequiredDescriptionDefault
asOfYes
claimsYes
maxAgeDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds a genuinely useful behavioral detail that checks can be flagged as future-dated as well as stale, but it says nothing about what the review produces, how results are ordered, or how malformed lines are handled, despite no output schema being present.

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?

A single front-loaded sentence with no filler. It is efficient, though it could absorb one or two more clauses about input format or output without becoming bloated.

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?

For a three-required-parameter tool with a structured free-text input, no output schema, and zero schema description coverage, the description is thin. It explains the review concept but not the expected line format, the result shape, or the interpretation of maxAgeDays boundary conditions.

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 0%, so the description must carry parameter meaning, and it only partially does: 'supplied review date' and 'freshness window' map to asOf and maxAgeDays, but the pipe-delimited 'Claim | source URL | checked date per line' format for claims is left to the schema title. The semantics of the most error-prone parameter are not reinforced.

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?

The description names a specific action (review logged sources) and a specific output concept (stale or future-dated evidence checks) scoped by a review date and freshness window. It is clearly distinguishable from unrelated siblings, though it doesn't explicitly differentiate itself from any near-equivalent verification tool.

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 explicit when-to-use guidance, no preconditions, and no mention of alternatives. The agent must infer that this is the tool to pick whenever evidence freshness matters, which is implied rather than stated.

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.