indico-mcp

Overview Schema Source Related Servers Discussions Admin

indico_list_registrations

Read-only

List registrations for a specific Indico event registration form, including state, payment, check-in, and tags. Use for attendee management and reporting.

Instructions

List registrations of a registration form (state, payment, check-in, tags).

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>"
    },
    "name": "indico_list_registrations"
  }
}

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.

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 already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful content context by naming the categories surfaced per registration, but says nothing about pagination, result volume, or permissions needed for the list.

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 sentence that front-loads the verb and resource and then qualifies the returned fields; no filler. Slightly terse for what is a key lookup tool, but structurally sound.

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. However, for a list tool with a mandatory form_id that is undocumented anywhere, the definition leaves a meaningful gap in how an agent is expected to obtain and use that parameter.

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 coverage is 67%: event_id and instance have clear descriptions, but form_id is undocumented in both schema and description. With the schema doing most of the work and no compensating detail in the description, the baseline 3 applies.

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 (List) and resource (registrations of a registration form), and parenthesizes the data categories returned (state, payment, check-in, tags). This distinguishes it from indico_get_registration (single) and indico_list_registration_forms (the forms themselves), though the sibling differentiation is implicit rather than stated.

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

Usage Guidelines2/5

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

No guidance on when to use this versus indico_get_registration or indico_list_registration_forms, and no prerequisite hint that a form_id must first be obtained from indico_list_registration_forms. Usage is only implied by the tool name.

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