Inspire Hep

Institutions Search

institutions_search

Read-onlyIdempotent

INSPIRE-HEP, the high-energy-physics literature database — search its institutions collection, the registry of physics laboratories, universities and research centres such as CERN, Fermilab and DESY. Takes a Lucene/Solr query and returns each institution's INSPIRE record id, ICN code, legal and display names, address and country. Answers what INSPIRE's record is for a physics laboratory or university.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`size`	No
`query`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "query": "CERN"
+  },
+  {
+    "query": "MIT Physics",
+    "size": 20
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Search results from INSPIRE-HEP institutions API",
+  "type": "object"
+}

First observedMay 14, 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, openWorld, idempotent, and non-destructive. The description adds meaningful behavioral context: it accepts a Lucene/Solr query (implying query syntax) and returns specific fields (id, ICN code, names, address, country). This goes beyond annotations without contradicting them.

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?

The description is two sentences, front-loading the purpose and key details. It includes examples and output fields. Slight redundancy in the last clause ('Answers what INSPIRE's record is...') but overall efficient.

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 annotations and an output schema present, the description covers the essential behavior: what it searches, how the query works, and what fields are returned. It does not explain the 'size' parameter or pagination, but the schema provides examples. Adequate for a simple 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 coverage is 0%, so description must compensate. It explains that 'query' is a Lucene/Solr query, adding semantics. However, 'size' is left unexplained, and the examples in the schema do not suffice. Partial compensation only.

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?

The description clearly states the tool searches the INSPIRE-HEP institutions collection, naming specific examples (CERN, Fermilab, DESY). It distinguishes itself from sibling search tools like authors_search and conferences_search by focusing on institutions. The verb 'search' and resource are explicit.

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 description provides clear context for when to use the tool: when seeking an institution's record in INSPIRE-HEP. It does not explicitly mention alternative tools or exclusions, but the purpose is specific enough to guide selection. No contradictory or misleading guidance given.

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

All Inspire Hep 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.