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 Brassica/canola/rapeseed/Camelina). 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 substance about search scope (ID matches only in open-access full text, name matches only in title/abstract, crop-limited) and about the per-result match-type flag. It does not disclose result ordering, truncation, or how the limit is applied.

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 sentences, front-loaded with the core action, followed by the two matching modes and a practical caveat. Dense but every clause carries information; no filler or repetition.

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 still conveys the shape of results (each paper carries a match-type indicator) and the matching rules behind them. Gaps remain around the undocumented limit parameter and result volume, but the core behavior needed to call it correctly is present.

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 parameter meaning. It clarifies that 'gene' can be resolved via IDs or names/symbols and what each matching mode covers, which is genuinely useful, but it says nothing about the accepted input format (ID vs symbol vs free text) and never mentions the 'limit' parameter at all.

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 gives a concrete verb and resource ('Papers mentioning a gene: Europe PMC search') and spells out exactly what is queried (gene IDs across all versions in open-access full text; name/symbols in title/abstract). It is unmistakable what the tool returns, though it never names a sibling (e.g. search_literature or get_paper) to sharpen the boundary.

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 context is implied clearly by 'papers mentioning a gene' plus the crop restriction (Brassica/canola/rapeseed/Camelina), and the closing caveat tells the agent to verify symbol collisions in the abstract. There is no explicit when-not guidance and no alternative tool named for broader or non-gene literature searches.

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