Skip to main content
Glama

Scholarly DOI metadata

bpj_scholarly_doi_metadata
Read-onlyIdempotent

Check basic DOI syntax and build scholarly article metadata with authors and publication date.

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": {
      "name": "<name>",
      "doi": "<doi>",
      "authors": "<authors>",
      "published": "<published>"
    },
    "name": "bpj_scholarly_doi_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
doiYes
nameYes
authorsYes
publishedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a side-effect-free, safe operation. The description adds that a DOI syntax check occurs, which is useful behavior, but it doesn't say what happens on an invalid DOI (error vs. a returned validity flag) or what the produced metadata looks like. For a builder tool with no output schema, that is a meaningful gap.

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 compact sentence with the validation action front-loaded ahead of the metadata construction. No filler, though the compound 'check ... and build' packs two behaviors into one clause without elaborating either.

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?

The tool is simple (four required string parameters, no nesting, no output schema), so the description covers the core intent. However, with zero schema description coverage and no output schema, it should at minimum clarify the expected input formats and the response shape or failure behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and all four parameters are required. The description only gestures at three of them (DOI, authors, publication date) and says nothing about acceptable date formats, author separators, or the purpose of 'name.' With no schema descriptions to lean on, the description does not compensate for the coverage gap.

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 specific verbs and resources: 'check basic DOI syntax' and 'build scholarly article metadata with authors and publication date.' This distinguishes it clearly from siblings like bpj_doi_reference_inventory and bpj_book_isbn_metadata, though it doesn't explicitly name an alternative.

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 guidance on when to use this versus the sibling DOI or book metadata tools, and no stated prerequisites. The only implied usage is that DOI syntax is validated, but nothing says what to do if validation fails or when this tool is the right choice.

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.