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

io.github.xngg1021/academic-research-kernel

by xngg1021

research_object_resolve

Resolve candidate bibliographic or identity records into discrete five-state equivalence judgments, helping determine whether metadata records refer to the same research object.

Instructions

Resolve and aggregate candidate bibliographic/identity records into discrete five-state equivalence judgments.

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": {
      "records": "<records>"
    },
    "name": "research_object_resolve"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordsYesList of candidate metadata records sharing possible identifiers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It hints at useful behavior by saying the output is 'discrete five-state equivalence judgments' and that records are 'aggregated', but never defines the five states, says whether the call is a pure read or records anything, or explains how conflicting candidates are treated. For a resolution/judgment tool with zero annotation coverage this is a substantial 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 front-loaded sentence with no filler and no repetition of the name. It is efficient, though the compressed jargon ('five-state equivalence judgments') spends words on a term it never unpacks.

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?

With no annotations, no output schema, and a free-form object array as input, the description is the only source of behavioral information, and it omits the definition of the five states and any description of the returned judgment structure. An agent can form the call but cannot predict or interpret the result confidently.

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 schema description coverage is 100%, so the schema already documents 'records' as a list of candidate metadata records sharing possible identifiers. The description adds no format, minimum-size, or identifier-consistency requirements beyond that, so it earns the schema-backed baseline rather than more.

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 has a specific verb pair ('Resolve and aggregate'), a specific resource ('candidate bibliographic/identity records'), and names the output form ('discrete five-state equivalence judgments'). It is clearly distinguishable from ingest/validate/trace siblings, but the key concept 'five-state' is left undefined, so the agent knows the shape of the operation better than its meaning.

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 use this versus alternatives such as research_lineage_trace or claim_evidence_validate, and no prerequisites or exclusions. The agent can only infer that it applies when it happens to hold a set of candidate records, which is not routing guidance.

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