cern-inspire-mcp-server

Search INSPIRE experiments

cern_inspire_search_experiments

Read-onlyIdempotent

Find experiments, collaborations, and facilities in INSPIRE-HEP (ATLAS, CMS, DUNE, Belle II, …) by name, accelerator, or INSPIRE legacy name (CERN-LHC-CMS); digits alone look up an experiment recid. Each record carries the accelerator, host institutions, collaboration and subgroups, classification, lifecycle dates (proposed, approved, started, completed, ongoing), INSPIRE's paper count, a description, and a literatureQuery to pass to cern_inspire_search_literature or cern_inspire_get_citation_summary for the experiment's papers.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Experiments to return (positive integer, default 5; above 25 uses 25).
`query`	Yes	Experiment, collaboration, accelerator, or facility name (ATLAS, LHCb, Tevatron), an INSPIRE legacy name (CERN-LHC-CMS), or an experiment recid (digits only).

Output Schema

Name	Required	Description
`cap`	No	The limit applied.
`error`	No	Present when the call failed. Absent on success.
`shown`	No	Number of records returned.
`notice`	No	Guidance on an empty or capped result.
`truncated`	No	True when more records matched than were returned.
`totalCount`	No	Total experiment records the query matched.
`experiments`	No	Matching experiment records, in INSPIRE relevance order.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / limit / description

Previous value: -"Experiments to return (1–25, default 5)."New value: +"Experiments to return (positive integer, default 5; above 25 uses 25)."

changedInput schema / properties / limit / maximum

Previous value: -25New value: +9007199254740991

First observedOct 2, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld, so the safety profile is covered. The description adds real value beyond that by enumerating the returned payload (accelerator, host institutions, collaboration and subgroups, classification, lifecycle dates, paper count, description) and the pass-through literatureQuery, which is genuine behavioral context.

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 sentences, front-loaded with the core action and lookup modes, then the return payload and chaining hint. Dense but every clause carries information; slightly long enumeration of returned fields keeps it from a 5.

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?

For a two-parameter search tool with full schema coverage, annotations, and an output schema, the description is more than sufficient. It redundantly enumerates return fields despite the output schema existing, which is harmless but slightly over-specified rather than a gap.

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 coverage is 100%, so both parameters are fully documented in the schema, establishing the baseline of 3. The description's explanation of query forms (including digits-as-recid) largely restates what the schema already says, adding no format or constraint detail beyond it.

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 (Find) and resource (experiments, collaborations, facilities in INSPIRE-HEP) with concrete examples (ATLAS, CMS, DUNE, Belle II). The accepted identifier forms (name, accelerator, legacy name, recid) make it immediately distinguishable from the literature and author search siblings.

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?

Explains how to query (name, accelerator, legacy name like CERN-LHC-CMS, or digits-only recid) and explicitly tells the agent to chain the returned literatureQuery into cern_inspire_search_literature or cern_inspire_get_citation_summary. It stops short of stating when NOT to use this tool versus the literature/author siblings, so a clear exclusion statement is missing.

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

All cern-inspire-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.