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 a legume crop or genus name). 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 declare read-only, idempotent, open-world, non-destructive behavior, so the bar is lower. The description still adds real behavioral context: the two distinct match modes, the restriction to open-access full text for ID matches, the requirement of a legume crop/genus name for symbol matches, and the known false-positive risk in symbol matching. It does not describe how the limit parameter governs result size or any ordering of returned papers.

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 sentences, front-loaded with the core purpose and then the matching mechanics; no filler. The parenthetical stacking ('all versions, in open-access full text') is dense but each clause carries non-obvious scoping information that earns its 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?

With only two parameters, no output schema, and annotations covering the safety profile, the description supplies what an agent needs: what is searched, how matches are classified, and how to interpret ambiguous symbol hits. The one material gap is the undocumented limit/pagination behavior, which matters for an agent deciding how many papers it will receive.

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 0%, so the description must carry the parameter burden. It does useful work for 'gene' by explaining that the input may be a gene ID (all versions) or a name/symbol, and that the two are matched against different fields. The 'limit' parameter is never mentioned, so half the schema remains 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?

The description states a specific verb and resource ('Papers mentioning a gene') and then specifies exactly which corpora and fields are searched: Europe PMC gene IDs across all versions in open-access full text, plus name/symbol matching in title or abstract. That is far more precise than a generic literature search. It stops short of naming a sibling such as search_literature or get_paper, so sibling differentiation is left implicit.

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 scoping rules: this tool is for gene-anchored literature retrieval, where name matches require a legume crop or genus name in the title/abstract. The note 'Name matches can be another gene with the same symbol: check the abstract' is actionable guidance on interpreting results. However, there is no explicit statement of when to prefer this over the general literature search or the single-paper retrieval tool.

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