Skip to main content
Glama
Sign In
PubCrawl

PubCrawl

by nickjlamb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

format_citation

Read-only

Format a PubMed citation into APA, Vancouver, Harvard, or BibTeX style using a PubMed ID.

Instructions

Format a citation for a PubMed article in APA, Vancouver, Harvard, or BibTeX style.

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": {
      "pmid": "<pmid>"
    },
    "name": "format_citation"
  }
}

Input Schema

NameRequiredDescriptionDefault
pmidYesPubMed ID
styleNoCitation styleapa

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.5.1

TDQS

A3.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the non-destructive and external-data aspects. However, the description does not disclose that the tool likely fetches article metadata from PubMed, what the return value looks like, or error behavior. It adds no behavioral context beyond the verb 'Format'.

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?

Single sentence, front-loaded with the action and resource, no filler.

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?

Given the simple 2-parameter shape, full schema documentation, and annotations covering safety and world interaction, the description is largely sufficient. It falls short only by not stating the return format, which is minor for such a tool.

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 100%, so all parameters are documented. The description reiterates the enumeration of styles already present in the schema, adding no new semantic meaning. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description names a specific verb 'Format', a precise resource 'citation for a PubMed article', and enumerates the four supported styles. This clearly distinguishes it from sibling search/retrieval tools.

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?

The description implies usage when a formatted citation is needed, but it does not explicitly state when to use it versus alternatives like search_pubmed or get_abstract, nor does it mention prerequisites such as a valid PMID. Context is implied, not stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools