Skip to main content
Glama

AutoTasker Hub — China Social Data API

pubmed_search

PubMed literature search (NCBI E-utilities): PMIDs + titles + journal + pubdate. $0.01 USDC.

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
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It usefully reveals the paid cost ($0.01 USDC) and the shape of returned fields (PMIDs, titles, journal, pubdate), which is real behavioral context, but says nothing about ordering, rate limits, error behavior, or what happens when zero results match.

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 compact fragments, front-loaded with the resource and backend, with zero filler. The terseness is efficient, though it shades into under-specification on parameters.

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

Completeness2/5

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

For a tool with no annotations, no output schema, and zero parameter documentation, the description is too thin. Listing return fields and cost helps, but query syntax and the meaning of `limit` remain undocumented anywhere in the definition.

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 description coverage is 0%, so the description must compensate and does not. It gives no hint about query syntax (PubMed field tags, MeSH terms, boolean operators) or what `limit` controls beyond the schema's default of 5 and maximum of 20.

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 ("PubMed literature search") plus the backend (NCBI E-utilities), which tells an agent exactly what corpus is queried. It also names the return fields, so it is distinguishable from generic search tools, but it never explicitly contrasts with siblings like arxiv_search or crossref_search.

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?

No guidance on when to choose this over the other scholarly search siblings, and no stated exclusions or prerequisites. The agent must infer from the word "PubMed" that this is the biomedical-literature option.

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.