Skip to main content
Glama
Sign In

OraFabric Medical Ontology Knowledge Base

by com.orafabric
OverviewDiscussionsAdmin

Get paper

get_paper
Read-onlyIdempotent

One paper and the findings extracted from it. Does not return the article text. $0.03.

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": {
      "id": "<id>"
    },
    "name": "get_paper"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA paper_id from an earlier result, a PMID or a DOI.
include_findingsNoReturn the findings extracted from this paper, not only its metadata. Turn it off when you only need the title, journal and year, for example when rendering a citation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / include_findings / description
      Added value: +"Return the findings extracted from this paper, not only its metadata. Turn it off when you only need the title, journal and year, for example when rendering a citation."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds two things annotations cannot: a scope boundary (no article text) and a price of $0.03, which is materially useful for agent budgeting. It does not say what happens when the id is unknown, keeping it short of a 5.

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?

Three very short clauses, front-loaded with what is returned before the exclusion and the price; nothing is filler. The first clause is a fragment without a verb, which costs a little clarity for an agent scanning for an action.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with no output schema, the description covers the essential unknowns: what comes back (paper plus findings), what does not (article text), and the cost. Parameter detail is fully handled by the schema, so nothing an agent needs to call this correctly is missing.

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%, so both parameters (id accepting paper_id/PMID/DOI, and include_findings toggling metadata-only) are already fully documented in the schema. The description adds no parameter-level meaning beyond that, so the baseline 3 applies.

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?

States the resource retrieved (one paper) and its payload (the findings extracted from it), and rules out article text, so an agent knows what it gets. The verb is implied rather than stated ('One paper and the findings...'), and no sibling is named, so differentiation from retrieve_evidence or explore_concept is left to inference.

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

Usage Guidelines3/5

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

Usage is implied by the required paper id and by the exclusion 'Does not return the article text', which warns against calling it when full text is needed. There is no explicit when-to-use statement and no mention of the sibling tools that could be alternatives for related retrievals.

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

All OraFabric Medical Ontology Knowledge Base toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources