Skip to main content
Glama
Sign In

cern-opendata-mcp-server

by io.github.cyanheads
OverviewDiscussionsAdmin

List Reference Vocabulary

cern_opendata_list_reference
Read-onlyIdempotent

Decode the vocabulary the other cern_opendata tools accept: experiments, record types, collision energies and types, file formats and data tiers, availability states, physics categories, LHCb magnet polarities and stripping streams and versions, identifier forms, query syntax, licensing, and the CMS run periods that have validated-run lists. Static and offline; omit topic for every table.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
topicNoOne table to return: experiments, record_types, collision_energies, collision_types, file_types, availability, categories, lhcb, identifiers, query_syntax, licensing or run_periods. Omit for every table.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when the call failed. Absent on success.
topicsNoThe requested table, or every table when topic is omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / topics / items / properties / entries / items / properties / value / description
      Previous value: -"A value or query form, spelled exactly as the tools accept it; in the identifiers and licensing topics, the name of an identifier form or a licensing rule."New value: +"Exact accepted value/query form; identifiers and licensing instead name identifier forms and licensing rules."
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and openWorld=false; the description reinforces this with 'static and offline' and adds the practically important default that omitting topic returns every table (a large response). Useful beyond the annotations, though it does not discuss response size or formatting further.

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 purpose clause is front-loaded and the enumeration maps directly to the enum values, so it earns its space. The single long sentence is dense, but every listed item corresponds to a real topic and the default behavior is stated up front.

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 an output schema present, the description doesn't need to explain return values, and for a one-parameter reference-lookup tool it covers what to pass and the omit-for-all default. Only the practical consequence of requesting all tables (response size) is left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the enum is self-documenting, so the baseline is 3. The description earns extra credit by expanding terse enum values ('lhcb' → magnet polarities, stripping streams and versions; 'run_periods' → the CMS run periods that have validated-run lists), giving meaning the schema alone lacks.

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 ('decode the vocabulary') and a precise resource (the controlled vocabularies the other cern_opendata tools accept), then enumerates the exact tables. This clearly separates it from the data-fetching siblings like get_records or search_records.

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 phrase 'the vocabulary the other cern_opendata tools accept' tells the agent exactly when this applies: resolving enum values before calling the sibling tools. 'Static and offline; omit topic for every table' gives a concrete default behavior. No explicit exclusions or named alternatives, which keeps it at 4.

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

All cern-opendata-mcp-server toolsInspect
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.

Resources