Skip to main content
Glama

Search the research archive

search_archive
Read-onlyIdempotent

Full-text search over indexed frontier research papers, clinical trials and research dossiers (AI, quantum computing, superconductivity, medicine, energy, astrophysics, mathematics). Returns ranked records with highlighted snippets, identifiers and links. Free.

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_archive"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
typeNoall
limitNo
queryYesSearch terms; use quotes for exact phrases.
topicNoOptional topic slug filter (see list_topics).
year_fromNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / kind / enum
      Previous value: -[
      -  "preprint",
      -  "article",
      -  "review",
      -  "trial"
      -]New value: +[
      +  "preprint",
      +  "article",
      +  "review",
      +  "trial",
      +  "report"
      +]
  2. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value beyond that: it says results are ranked with highlighted snippets, identifiers and links, and that access is free (no cost/auth barrier). It does not mention pagination or result-count caps.

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 compact sentences with the query scope front-loaded first, then the return shape, then the cost note. No filler, and each sentence carries distinct 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?

With six parameters at 33% schema coverage and no output schema, the description is adequate on the return side but thin on filters and selection routing. An agent would still not know how 'kind' and 'type' interact, what the limit ceiling means in practice, or when to prefer direct-fetch siblings.

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 only 33%, so the description must compensate and it does not — it says nothing about kind, type, limit or year_from. The potentially confusing overlap between the 'kind' enum (preprint/article/review/trial/report) and the 'type' enum (all/papers/dossiers) is left entirely unexplained.

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+resource ('Full-text search over indexed frontier research papers, clinical trials and research dossiers') and enumerates the covered domains, which clearly separates it from retrieval siblings like get_paper or get_dossier. It never names a sibling explicitly, so it stops short of full differentiation.

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?

The description gives no when-to-use or when-not-to-use guidance, and does not point to alternatives such as get_paper/get_dossier for direct retrieval or list_topics for browsing. The only implied usage cue is that this is a search entry point, which the agent must infer.

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