indico-mcp

Overview Schema Source Related Servers Discussions Admin

indico_list_category_events

Read-only

Retrieve events from an Indico category and its subcategories within a date range, with optional filters and result limits.

Instructions

List events in a category (and its subcategories) within a date range.

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": {
      "category_id": "<category_id>"
    },
    "name": "indico_list_category_events"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`to_date`	No	YYYY-MM-DD, 'today', or relative like '+30d'
`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.
`from_date`	No	YYYY-MM-DD, 'today', or relative like '-30d'	today
`category_id`	Yes	Category id; 0 is the root, covering the whole instance
`newest_first`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 27, 2026

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description does add one behavioral trait beyond annotations: that subcategories are included recursively. However, it says nothing about pagination or limit behavior, so it only partially enriches the picture.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with the scope front-loaded and zero filler. Every clause earns its place.

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 values need not be explained, and annotations cover safety. But for a listing tool with six parameters, the description omits sibling differentiation and pagination ordering context, leaving notable gaps.

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%, so several parameters (to_date, instance, from_date, category_id) carry their own descriptions in the schema. The tool description adds no parameter-level meaning, leaving limit and newest_first undocumented. Baseline 3 is appropriate given the schema does most of the work.

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 ('events') with clear scope: a category and its subcategories within a date range. This is precise, though it does not name a sibling to distinguish itself from indico_search_events or indico_get_timetable.

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 when-to-use guidance or alternatives are given. The phrase 'within a date range' implies a filtered-listing use case, but an agent is left to infer when this beats indico_search_events. Neither exclusions nor prerequisites are stated.

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