Skip to main content
Glama

Reference DOI inventory

bpj_doi_reference_inventory
Read-onlyIdempotent

Extract common DOI forms and remove trailing sentence punctuation and unmatched closing parentheses.

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>"
    },
    "name": "bpj_doi_reference_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add transformation detail, which it does by naming the cleanup rules for trailing punctuation and unmatched closing parentheses. However it says nothing about deduplication, ordering, or what happens to input exceeding the 6000-character cap, leaving real behavioral questions open.

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 sentence with no filler, front-loading the extraction action before the cleanup rule. 'Common DOI forms' is slightly vague about which forms qualify, which keeps it from being fully precise.

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 no output schema, the description carries the burden of describing the return value, and it does not say whether results are a list, deduplicated, or ordered, nor whether the cleaned matched strings or the DOI alone are returned. For a single-parameter extraction tool the gap is modest but real.

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?

There is only one parameter and it is self-explanatory ('text', titled 'Source text'), so the schema does most of the work despite 0% description coverage. The description implies the parameter is the text to scan but adds no constraint detail beyond what the schema already states.

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 and resource ('Extract common DOI forms') plus a normalization rule, so it is clearly distinguishable from a plain inventory scan. It does not distinguish itself from siblings such as bpj_scholarly_doi_metadata, which an agent might reasonably confuse with DOI handling, but the purpose itself is unambiguous.

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: give it text, get DOIs back. There is no statement of when to prefer this over the scholarly-DOI metadata sibling, no note on input expectations (plain text vs. HTML/markdown that already have dedicated reference tools), and no exclusions.

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.