Skip to main content
Glama

gene_papers

Read-onlyIdempotent

Papers mentioning a gene: Europe PMC search for its gene IDs (all versions, in open-access full text) and its name/symbols (in title or abstract, with wheat/Triticum/Aegilops). Each paper says whether it matched an ID or a name. Name matches can be another gene with the same symbol: check the abstract.

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": {
      "gene": "<gene>"
    },
    "name": "gene_papers"
  }
}

Input Schema

NameRequiredDescriptionDefault
geneYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world, non-destructive, so the bar is lower; the description still adds real behavioral context: IDs are searched across all versions in open-access full text while names/symbols are searched only in title or abstract, results are taxon-restricted, and each result carries a match-type indicator. It also warns that symbol matches can be a different gene, prompting abstract verification.

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?

Two tight sentences with the core action front-loaded and the caveat last. Dense but every clause carries information; the match-type and false-positive caveat earn their place.

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?

No output schema exists, and the description compensates by explaining what each result contains (matched by ID vs. name) and the reliability caveat. The only meaningful gap is result-volume behavior (what limit does, pagination), which matters for a search tool returning an unbounded paper set.

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% with two parameters, so the description must compensate. It usefully explains what the 'gene' input means (gene IDs, all versions, plus name/symbols), but the 'limit' parameter (default 20) is never mentioned, leaving one of two parameters undocumented.

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+resource ('Papers mentioning a gene') and immediately specifies the retrieval mechanism (Europe PMC search). It is clearly a literature-lookup tool, distinguishable from gene-expression/function siblings, though it never explicitly contrasts itself with search_literature or get_paper.

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 rather than stated: the description defines what gets searched and under what taxonomic restriction (wheat/Triticum/Aegilops), which tells an agent the tool is scoped to wheat gene literature. There is no explicit when-to-use/when-not statement and no routing to sibling literature tools.

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.

Resources