indico-mcp

Overview Schema Source Related Servers Discussions Admin

indico_update_session

Modify an Indico session by updating its title, description, code, or default contribution length for a given event and session.

Instructions

Change a session's title, description, code or default contribution length.

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

Input Schema

Name	Required	Description
`code`	No
`title`	No
`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.
`session_id`	Yes
`description`	No
`default_contribution_minutes`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 27, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context beyond listing updatable fields: it does not mention permissions, side effects, default handling, or what happens when optional fields are omitted.

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 description is a single front-loaded sentence with no wasted words. It is appropriately sized but very terse for a mutation tool with seven parameters and low schema description coverage.

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?

For a simple update tool with an output schema and annotations covering safety, the description is minimally viable. It identifies the update fields but does not cover required identifiers, instance handling, or sibling differentiation, leaving notable gaps for an agent with many similar tools available.

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 description coverage is only 29%, so the description should compensate. It names four updatable fields (title, description, code, default contribution length) corresponding to optional parameters, but omits required event_id/session_id and instance, and adds no format or constraint details beyond the schema.

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?

The description states a specific verb ('Change') and resource ('a session's title, description, code or default contribution length'), making the operation clear. However, it does not distinguish this tool from sibling update tools such as indico_update_session_block or indico_update_event.

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?

The description gives no when-to-use guidance, no prerequisites, and no alternatives. An agent must infer that this is the correct tool for modifying an existing session rather than creating one or updating a session block.

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