Skip to main content
Glama

Numbered reference coverage

bpj_numbered_reference_coverage
Read-onlyIdempotent

Cross-check bracketed numeric citations and hyphenated ranges against a numbered bibliography.

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": {
      "text": "<text>",
      "references": "<references>"
    },
    "name": "bpj_numbered_reference_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
referencesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/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=false, so the safety profile is fully covered. The description adds the useful behavioral detail that hyphenated ranges are expanded and checked, but says nothing about what the cross-check reports (missing entries, orphaned references) or how partial mismatches are handled.

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 the verb first and no filler. It earns its place, though the extreme terseness leaves gaps that a second short sentence about the returned findings could have closed.

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

Completeness2/5

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

For a validation/coverage tool with no output schema and zero parameter description coverage, the definition should say what the result contains and what counts as a mismatch. Neither is present, so an agent cannot predict the return shape or interpret a successful versus failing run.

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% and the description does partially compensate, mapping one input to bracketed citations in source text and the other to numbered bibliography lines. It still adds no format specifics—no citation syntax, separator rules, or numbering expectations—so an agent must infer conventions from the schema titles.

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 gives a specific verb ("Cross-check") and names concrete resources: bracketed numeric citations, hyphenated ranges, and a numbered bibliography. That is far better than restating the title, but it offers no contrast with related reference-coverage tools, so an agent cannot tell from the text alone when this differs from a markdown or DOI reference checker.

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, when-not-to-use, or alternative-tool guidance. The named resource types imply the scenario (numeric-style citations paired with a numbered list), but an agent gets no statement of prerequisites, limits, or which sibling to prefer for other citation styles.

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.