Skip to main content
Glama

FoxAPIs data sources

PubMed search

pubmed_search
Read-onlyIdempotent

Search PubMed by keyword; returns papers with title, authors, journal, date and PubMed link. Costs 5 credits a call; an answer with no data is not charged. Needs your FoxAPIs key (free to start).

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": {
      "query": "<query>"
    },
    "name": "pubmed_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNorelevance
queryYesFor example: "crispr"
date_fromNo
max_resultsNoFor example: 3

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a per-call credit cost, the fact that empty results are free, and the FoxAPIs key requirement. It does not describe result ordering, paging, or rate limits, so it is good but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short clauses, front-loaded with the action and the return shape, then cost and auth. No filler or repetition; every sentence carries new information.

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

Completeness3/5

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

For a simple read-only search tool with no output schema, the description covers the return fields, cost model, and auth requirement adequately. It is thin precisely where the tool is most configurable, though: filtering, sorting, and result-count limits are left entirely to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 50% and the description ignores half the parameters. It never explains 'sort' (relevance vs. date), 'date_from' format or semantics, or any cap on 'max_results', so the undocumented parameters remain unexplained in both places.

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 a specific verb and resource ('Search PubMed by keyword') and even enumerates the return fields (title, authors, journal, date, link). It does not distinguish itself from the many sibling search tools (academic_paper, biorxiv_preprints, clinicaltrials_search) that could also satisfy a literature query.

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

Usage Guidelines2/5

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

There is no guidance on when to choose PubMed over the sibling academic, preprint, or trial search tools, and no stated exclusions or prerequisites besides the API key. The only usage-adjacent content is billing ('Costs 5 credits a call'), which tells the agent the price but not the selection criteria.

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