Skip to main content
Glama

cern-opendata-mcp-server

Get CERN Open Data Analysis Environment

cern_opendata_get_analysis_env
Read-onlyIdempotent

Assemble what is needed to analyse a record: its container images, CMSSW release and global tag; the condition-data, VM and validated-run records for its run periods; example software that declares it works with the record; and quoted sections of the guides the record links (the first two are fetched). Container images, software and guide code are licensed separately from the CC0 data. Use cern_opendata_list_files for the record's files.

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": {
      "recid": "<recid>"
    },
    "name": "cern_opendata_get_analysis_env"
  }
}

Input Schema

NameRequiredDescriptionDefault
recidYesRecord id: up to 12 digits (6004), optionally after a lowercase experiment prefix (cms-93956). cern_opendata_search_records and cern_opendata_get_records return it.

Output Schema

NameRequiredDescriptionDefault
typeNoPortal record classification.
errorNoPresent when the call failed. Absent on success.
recidNoThe record id.
titleNoRecord title.
guidesNoEvery portal guide linked in the usage section.
noticeNoGaps and next steps: empty environment, unread or excess linked records, unfetched/missing/cut guides or unmatched guide anchors; absent when none.
softwareNoThe record's own software environment (system_details).
experimentNoExperiments the record belongs to.
run_periodNoRun periods the record covers, such as Run2012B.
other_linksNoOther usage links, e.g. getting-started pages.
license_noteNoHow the environment is licensed.
example_softwareNoSoftware records that declare they work with this record.
environment_recordsNoCondition, VM and validation records for the run periods, and others linking here.
separately_licensedNoImages, software and guide code have separate licenses from CC0 data.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changed
    • changedOutput schema / properties / environment_records / items / description
      Previous value: -"One Environment record for this record (condition data, VM, validation)."New value: +"Linked Environment record: condition data, VM or validation."
    • changedOutput schema / properties / example_software / items / properties / license_id / description
      Previous value: -"License the software record states (such as GPL-3.0-only); absent when none."New value: +"Stated software license (e.g. GPL-3.0-only); absent when none."
    • changedOutput schema / properties / guides / items / properties / fetched / description
      Previous value: -"False when the guide was not fetched (only the first two are) or was not found; notice says which."New value: +"False if unfetched (only the first two are fetched) or not found; notice distinguishes them."
    • changedOutput schema / properties / guides / items / properties / reference_definitions / description
      Previous value: -"The guide's [label]: destination lines from outside the section whose label a [...] span of the section uses: verbatim, in body order, the first per label; a definition past a cut counts as outside. Empty when the section uses none; absent when the guide was not fetched."New value: +"External [label]: destination definitions used by [...] spans in section: verbatim, body order, first per label. Includes definitions past a cut. Empty when unused; absent when unfetched."
    • changedOutput schema / properties / guides / items / properties / section / description
      Previous value: -"The linked section (or the opening section) as markdown, as the portal sent it but with LF line ends; at most 12,000 characters."New value: +"Linked or opening section: original markdown with LF line ends, up to 12,000 characters."
    • changedOutput schema / properties / guides / items / properties / section_truncated / description
      Previous value: -"True when the section was cut at 12,000 characters; the notice names the body_offset where the quote stops."New value: +"Section cut at 12,000 characters; notice gives body_offset where the quote stops."
    • changedOutput schema / properties / guides / items / properties / slug / description
      Previous value: -"Doc slug; pass it as the one id of cern_opendata_get_records for the page body, with body_offset to read on past a cut (the notice names the offset)."New value: +"Doc slug: pass as the sole cern_opendata_get_records id for its body; body_offset continues a cut at the offset in notice."
    • changedOutput schema / properties / notice / description
      Previous value: -"What could not be assembled and how to get it: an empty environment, linked records that could not be read, guides not fetched, not found or cut, a guide anchor no heading carries, or more linked records than shown."New value: +"Gaps and next steps: empty environment, unread or excess linked records, unfetched/missing/cut guides or unmatched guide anchors; absent when none."
    • changedOutput schema / properties / other_links / description
      Previous value: -"The other usage links (getting-started pages and the like)."New value: +"Other usage links, e.g. getting-started pages."
    • changedOutput schema / properties / separately_licensed / description
      Previous value: -"Always true: images, software and guide code are licensed apart from the CC0 data."New value: +"Images, software and guide code have separate licenses from CC0 data."
    • changedOutput schema / properties / software / properties / container_images / description
      Previous value: -"Container images for the environment; empty when the record lists none."New value: +"Environment images; empty when none listed."
    • changedOutput schema / properties / software / properties / environment_recid / description
      Previous value: -"Recid of the environment (VM or container) record, when stated."New value: +"Stated VM/container environment recid."
    • changedOutput schema / properties / type / description
      Previous value: -"Record type as the portal classifies it."New value: +"Portal record classification."
    • changedOutput schema / properties / type / properties / primary / description
      Previous value: -"Primary type: Dataset, Software, Environment, Documentation, Supplementaries or News. Empty when the record states none."New value: +"Dataset, Software, Environment, Documentation, Supplementaries or News; empty when unstated."
    • changedOutput schema / properties / type / properties / secondary / description
      Previous value: -"Secondary types, such as Collision or Simulated; empty when none."New value: +"Secondary types (Collision, Simulated, etc.); empty when none."
  2. Changed2 schema fields changed
    • changedInput schema / properties / recid / description
      Previous value: -"Record id: up to 12 digits (6004), optionally after an experiment prefix (cms-93956); recid:6004 or a portal record URL also work. cern_opendata_search_records and cern_opendata_get_records return it."New value: +"Record id: up to 12 digits (6004), optionally after a lowercase experiment prefix (cms-93956). cern_opendata_search_records and cern_opendata_get_records return it."
    • addedOutput schema / properties / guides / items / properties / reference_definitions
      Added value: +{
      +  "description": "The guide's [label]: destination lines from outside the section whose label a [...] span of the section uses: verbatim, in body order, the first per label; a definition past a cut counts as outside. Empty when the section uses none; absent when the guide was not fetched.",
      +  "items": {
      +    "description": "One definition line, verbatim.",
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
  3. 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/openWorld/idempotent, so safety is covered; the description adds genuinely new context beyond that — it discloses that quoted guide sections are produced and that only the first two are fetched, plus a licensing caveat for images/software/guide code. It doesn't warn about latency or partial results, but output schema exists to cover return values.

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?

Front-loaded with the assembled artifacts and efficient for how much it packs in. The phrase 'the first two are fetched' is slightly ambiguous about which two of the preceding items it refers to, costing a bit of clarity.

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 composite aggregation tool, the description is complete enough: annotations carry the safety profile, an output schema exists for return shape, and the schema fully documents the one parameter. Only the fetch-latency and missing-data failure modes are unaddressed, which is minor.

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?

There is a single parameter and schema coverage is 100%: the schema documents the recid pattern and even names the sibling tools that produce it. The description adds no further meaning about the identifier, so the baseline 3 for high schema coverage is appropriate.

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 names a specific verb ('assemble') and enumerates the concrete artifacts produced: container images, CMSSW release, global tag, condition-data/VM/validated-run records, example software, and quoted guide sections. This is clearly distinct from the sibling list_files tool, which is explicitly excluded.

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?

It gives a clear context (preparing to analyse a record) and names an explicit alternative for a neighbouring need: 'Use cern_opendata_list_files for the record's files.' It does not discuss when this tool is overkill or what happens for records lacking these artifacts, but the routing guidance is solid.

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.