Skip to main content
Glama
io.github.xngg1021/academic-research-kernel

io.github.xngg1021/academic-research-kernel

by xngg1021

academic_verify_source

Normalize DOI, arXiv, PMID, PMCID, or OpenAlex identifiers and cross-verify their metadata across OpenAlex and Crossref to confirm source accuracy.

Instructions

Normalize scholarly identifiers (DOI, arXiv, PMID, PMCID, OpenAlex) and cross-verify metadata across OpenAlex and Crossref records.

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": {
      "identifier": "<identifier>"
    },
    "name": "academic_verify_source"
  }
}

Input Schema

NameRequiredDescriptionDefault
offlineNoDisable network requests
identifierYesDOI, arXiv ID, PMID, OpenAlex ID, or URL
normalize_onlyNoOnly normalize the identifier without querying metadata
crossref_recordNoOptional pre-fetched Crossref message JSON object
openalex_recordNoOptional pre-fetched OpenAlex work JSON object

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden, and it discloses only that two external services (OpenAlex, Crossref) are consulted. It does not state that the tool is read-only, what happens when the two sources disagree, how unresolvable identifiers are reported, or whether network access can be avoided. Those are exactly the traits an agent needs before calling a cross-verification tool.

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 a specific verb pair and object list, no filler or redundancy. Every clause carries information.

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 five-parameter tool with nested object inputs and no output schema, the description leaves the response shape undefined — it never says whether the result is a canonical identifier, merged metadata, or a discrepancy report. It also ignores the two modes (normalize_only, offline) that materially change what the call does. Adequate to identify the tool, insufficient to predict its behavior.

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 100%, so parameter meaning is already documented in structured fields; the description adds little beyond confirming the identifier families and the Crossref/OpenAlex cross-check rationale. The optional pre-fetched record objects and the offline/normalize_only modes are not explained in the description at all. Baseline 3 applies when the schema does the heavy lifting.

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 two concrete operations (normalize identifiers, cross-verify metadata) and enumerates the identifier systems (DOI, arXiv, PMID, PMCID, OpenAlex) plus the two data sources (OpenAlex, Crossref). An agent can tell it is an identifier-normalization/verification tool rather than a generic resolver. It stops short of distinguishing itself from lookalike siblings such as research_object_resolve.

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 statement of when to choose this tool versus an alternative, and no prerequisites or exclusions are given. The only usage signals are implicit in parameter names (normalize_only, offline) which the description never references. An agent must infer the use case entirely.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.