Skip to main content
Glama

Conferences Search

conferences_search
Read-onlyIdempotent

INSPIRE-HEP, the high-energy-physics literature database, search its conferences collection of particle-physics meetings, workshops and schools. Takes a Lucene/Solr query and returns each event's INSPIRE record id, title and acronym, opening and closing dates, location, series and proceedings links. Answers when and where a physics conference is or was held.

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": "string theory"
    },
    "name": "conferences_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": "string theory"
      +  },
      +  {
      +    "query": "ICHEP 2023",
      +    "size": 15
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "description": "Search results from INSPIRE-HEP conferences API",
      +  "type": "object"
      +}
  2. First observed

TDQS

A4/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 open-world behavior, so the safety profile is covered. The description adds useful context beyond them: the query must be Lucene/Solr syntax and results are conference events. It says nothing about pagination, result caps, or whether `size` truncates silently.

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?

Three front-loaded sentences: identity, mechanics, then the question it answers. Efficient overall, though the enumeration of returned fields overlaps with the existing output schema and could be trimmed.

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?

Return values are covered by the output schema, so the description is complete on the output side. The gap is on the input side: for a tool with no schema parameter descriptions, the description should at least explain `size` (default, max, pagination), which it does not.

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?

The description adds real meaning for the required `query` parameter by specifying the Lucene/Solr dialect, which the schema does not. However, with 0% schema description coverage, the second parameter `size` is left completely uncharacterized—no default, no maximum, no statement that it controls result count.

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 its conferences collection of particle-physics meetings, workshops and schools') and scopes it to a named database, INSPIRE-HEP. The final sentence, 'Answers when and where a physics conference is or was held,' makes the intended question unambiguous and separates it from paper/author/institution 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?

Gives clear context for when the tool applies: questions about when and where a physics conference occurred. It does not name an alternative (e.g., a literature or author search) or state exclusions, so the agent must infer the routing itself.

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.