Skip to main content
Glama
GMPSignal MCP Server

GMPSignal MCP Server

search_scientific_literature_citations

Read-onlyIdempotent

Search peer-reviewed papers, preprints, DOIs, abstracts, and citation metrics across OpenAlex, Semantic Scholar, Crossref, and arXiv to find relevant research and assess impact.

Instructions

Search peer-reviewed scientific papers, preprints, citation velocity, author h-index metrics, DOIs, OpenAccess PDFs, and abstracts across OpenAlex, Semantic Scholar, Crossref, and arXiv.

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": "search_scientific_literature_citations"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesResearch topic, paper title, author name, or DOI to search.Large Language Model Agents
fromYearNoEarliest publication year to include.
maxResultsNoMaximum number of academic publication records to return.
minCitationsNoMinimum citation count threshold.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.3.2

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered without description help. The description adds genuine context by disclosing that results are federated across OpenAlex, Semantic Scholar, Crossref, and arXiv, implying cross-source variation in PDF and abstract availability. It stops short of saying how results are merged, de-duplicated, or ordered, and gives no latency or per-source limit behavior.

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?

A single front-loaded sentence that opens with the verb and resource before listing modifiers, so the essential claim lands first. The field enumeration is somewhat list-heavy but each item (h-index, DOI, OA PDF) carries real discriminating information for an agent deciding relevance.

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 four fully documented parameters, an explicit annotation set, and no output schema, the description does the one thing it most needs to do: enumerate the categories of data returned, effectively substituting for a missing output schema. It omits result ordering, pagination, and cross-source merging behavior, which is a modest but real gap for a federated search 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%, with query, fromYear, maxResults, and minCitations all documented in-schema, so the baseline of 3 applies. The description adds no additional meaning about these parameters — the enumerated items (citation velocity, h-index, DOIs) are output data types, not inputs, so nothing compensates or extends beyond the schema.

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?

States a specific verb ("Search") plus a precisely scoped resource (peer-reviewed papers, preprints, citation metrics, DOIs, OA PDFs, abstracts) and names the four upstream sources. This is unambiguously distinguishable from every listed sibling, which cover tenders, FDA compliance, SEC filings, crypto, startups, and sanctions rather than academic literature.

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

Usage Guidelines4/5

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

The domain framing makes the intended use clear (scholarly/academic literature lookup), and no sibling overlaps that domain, so no routing exclusions are strictly needed. However, the description never states when NOT to use it (e.g., non-academic or general web queries) and offers no alternative-tool steering.

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