Skip to main content
Glama

Check an ORCID identifier

bpj_orcid_validate
Read-onlyIdempotent

Validate the MOD 11-2 check character of an ORCID researcher identifier.

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": {
      "value": "<value>"
    },
    "name": "bpj_orcid_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that validation targets the check character specifically, which is real behavioral context, but it says nothing about how malformed input or a bare-vs-URL ORCID is handled, nor what the result looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the discriminating detail (MOD 11-2 check character) arrives immediately. Nothing redundant or padded.

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 and annotations are rich, but with no output schema the description should indicate what a pass/fail return looks like. Acceptable-input form is also unaddressed, so an agent could call it with a shape that fails for unintended reasons.

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 coverage is 0% and the schema only offers 'Input value' with a maxLength of 240, so the description is the sole source of meaning — and it does clarify that the value is an ORCID researcher identifier. However, it does not state whether the canonical hyphenated form, a bare 16-character iD, or a full https://orcid.org/ URL is expected, which is the main ambiguity for this parameter.

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?

Names a specific verb ('Validate'), a specific resource ('ORCID researcher identifier') and even the algorithm ('MOD 11-2 check character'), so an agent knows this is a checksum/format-integrity test rather than a lookup or metadata fetch. It does not explicitly name or contrast a sibling, but the check-character scope keeps it clearly distinct from generic identifier-shape or registry tools.

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 when-to-use guidance, no prerequisite, and no mention of alternatives such as a shape check or a registry lookup. The agent must infer from the name alone how this fits into a validation workflow.

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.