Skip to main content
Glama
Sign In
indico-mcp

indico-mcp

by vuillaut
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

indico_create_session

Create a new session in an Indico event to group related talks or contributions, then add its time slot separately with indico_create_session_block.

Instructions

Create a session. It has no time slot until you add one with indico_create_session_block.

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

Input Schema

NameRequiredDescriptionDefault
codeNoBook of abstracts code; conferences only
titleYes
event_idYesIndico event id (the number in /event/<id>/)
instanceNoIndico 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.
descriptionNo
default_contribution_minutesNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/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 useful behavioral context beyond annotations by revealing that the created session initially has no time slot and requires indico_create_session_block for scheduling. It does not contradict the annotations.

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?

The description is two short sentences, front-loaded with the core action and followed by a critical workflow detail. Every sentence earns its place with no redundancy or filler.

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?

Given that an output schema exists and annotations cover safety, the description supplies the key scheduling dependency an agent needs to act correctly. It is complete enough for invocation, though it could still mention parameter expectations or permissions more explicitly.

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?

The description adds no information about any of the six parameters. With only 50% schema description coverage, the description does not compensate for undocumented parameters such as title, description, or default_contribution_minutes. It leaves parameter semantics entirely to the input schema.

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 states a specific verb and resource: 'Create a session.' It also distinguishes the initial state from a session block by noting the session has no time slot until indico_create_session_block is used. An agent can identify the tool's purpose and relationship to the sibling tool without inspecting schemas.

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?

The description gives a clear workflow dependency: create a session first, then use indico_create_session_block to assign a time slot. This helps an agent understand the required sequence. However, it does not explicitly state when to use this tool versus update_session or other create tools, nor does it mention exclusions.

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

Deploy Server

Other Tools