Skip to main content
Glama

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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "CERN"
    },
    "name": "institutions_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNo
queryYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
      +}
  2. First observed

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 and non-destructive, so safety is covered. The description adds meaningful behavior beyond them: it accepts a Lucene/Solr query and discloses the returned fields (INSPIRE record id, ICN code, legal/display names, address, country). Pagination/ranking behavior of the 'size' parameter is not discussed, keeping it below a 5.

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 dense sentences with no filler, though the opening clause is slightly awkwardly constructed ('INSPIRE-HEP, the ... database, search its institutions collection'). The purpose and return contents are front-loaded effectively.

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?

An output schema exists, so the description's summary of returned fields is a bonus rather than a requirement. Query syntax is covered; the only real gap is the undocumented 'size' parameter and any guidance on result volume.

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 0%, so the description must carry parameter meaning. It usefully states that the query is a Lucene/Solr query, which is real syntax information beyond the schema, but the 'size' parameter is left entirely undefined in both schema and description.

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 and resource (search INSPIRE-HEP's institutions collection) and defines the resource concretely as the registry of physics laboratories, universities and research centres with named examples (CERN, Fermilab, DESY). The closing line, 'Answers what INSPIRE's record is for a physics laboratory or university,' further distinguishes it from literature/author/conference 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?

Clear usage context: it is the lookup for identifying an institution's INSPIRE record and its identifiers. There are no explicit exclusions or named alternatives, but the resource scope makes the when-to-use condition evident without ambiguity.

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.