indico-mcp

by vuillaut

Overview Schema Source Related Servers Discussions Admin

Python

Remote

indico_get_registration

Read-only

Retrieve a specific event registration and its form field answers using event, form, and registration IDs.

Instructions

Get one registration, including the answers to the form fields.

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": {
      "event_id": "<event_id>",
      "form_id": "<form_id>",
      "registration_id": "<registration_id>"
    },
    "name": "indico_get_registration"
  }
}

Input Schema

Name	Required	Description
`form_id`	Yes
`event_id`	Yes	Indico event id (the number in /event/<id>/)
`instance`	No	Indico instance: a configured name (see indico_list_instances) or its URL; an event link works too. Can be left out when only one instance is configured or a default is set.
`registration_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 27, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations supply readOnlyHint=true and openWorldHint=true, so the safety profile is already covered and the bar is lower. The description usefully discloses that form-field answers are part of the payload, but says nothing about permissions required, error behavior for missing ids, or pagination/volume concerns, and an output schema already covers return shape.

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?

A single front-loaded sentence with zero filler, which is appropriate for a simple lookup tool. It is arguably too terse for the parameter gaps it leaves behind, but nothing in the text is wasted.

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?

An output schema exists, so return-value detail is not required, and a four-parameter read tool is low complexity. However, with two required parameters undocumented and no usage guidance, the definition is only minimally sufficient for correct invocation.

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

Parameters2/5

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

Schema description coverage is only 50%: event_id and instance carry descriptions, while form_id and registration_id are bare integers with no explanation anywhere. The description adds no parameter meaning at all, leaving the two undocumented required identifiers unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get one registration') and adds the scope detail that form-field answers are included. It implicitly separates itself from indico_list_registrations by saying 'one', but it does not name any sibling or explicitly distinguish the singular case.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: needing a single registration by id, including its form answers. There is no explicit when-to-use statement, no mention of when to prefer indico_list_registrations or indico_list_registration_forms, and no prerequisites such as permissions on the event.

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