Skip to main content
Glama

Pubtator Relation Evidence

pubtator_relation_evidence
Read-onlyIdempotent

The supporting passages behind one specific PubTator 3 relation, every paper whose text the model read the relation from, with the matched sentence, both entities' mentions, PMID, journal and date. Give the relation type and both entities (ids or plain names); page through the results 10 at a time. Use after pubtator_relations to audit a predicted relation. Sourced from the PubTator 3 search index at NCBI/NLM; the relation itself is machine-extracted, not curated. Keyless.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "page": 1,
      "type": "associate",
      "entity1": "@GENE_BRCA1",
      "entity2": "@DISEASE_Breast_Neoplasms"
    },
    "name": "pubtator_relation_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page, 1-based (default 1). 10 passages per page.
typeYesRelation type, e.g. "treat", "associate", "inhibit".
entity1YesFirst entity, PubTator id or plain name, e.g. "@CHEMICAL_Doxorubicin".
entity2YesSecond entity, PubTator id or plain name, e.g. "@DISEASE_Breast_Neoplasms". Order does not matter.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / entity1 / description
      Previous value: -"First entity — PubTator id or plain name, e.g. \"@CHEMICAL_Doxorubicin\"."New value: +"First entity, PubTator id or plain name, e.g. \"@CHEMICAL_Doxorubicin\"."
    • changedInput schema / properties / entity2 / description
      Previous value: -"Second entity — PubTator id or plain name, e.g. \"@DISEASE_Breast_Neoplasms\". Order does not matter."New value: +"Second entity, PubTator id or plain name, e.g. \"@DISEASE_Breast_Neoplasms\". Order does not matter."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely useful context beyond that: pagination at 10 passages per page, keyless access, the NCBI/NLM search-index provenance, and the important caveat that the relation is machine-extracted rather than curated — a trust signal an agent should account for. It stops short of describing empty-result or non-found behavior.

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?

Front-loaded with what is returned, followed by invocation, then usage routing and provenance. Dense but every clause carries information; the only mild redundancy is repeating the 10-per-page paging already in the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 takes on the job of enumerating returned fields, and it does so. It also covers provenance and auth. Remaining gaps are minor: what happens when no passages exist for a relation, and whether highly-cited relations are truncated beyond the paged window.

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 description coverage is 100%, and the schema already documents page (1-based, 10 per page), the relation-type enum, and that entities may be a PubTator id or plain name with order not mattering. The description restates the same facts ('ids or plain names', 'page through the results 10 at a time') rather than adding format or matching rules, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource — retrieving the supporting passages behind one PubTator 3 relation — and enumerates the payload (matched sentence, both entity mentions, PMID, journal, date). The opening sentence makes clear it is a narrow drill-down on a single relation, which distinguishes it from the sibling pubtator_relations used to discover relations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use after pubtator_relations to audit a predicted relation', naming the alternative and the condition that selects it. The invocation recipe (give relation type and both entities, as ids or plain names) is also stated, leaving little to inference.

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.