Skip to main content
Glama
cohm

indico-mcp

by cohm

find_available_rooms

Find free rooms in a specific location and time window by checking room booking data. Use optional name filter to target a specific room or building wing.

Instructions

List rooms that are NOT already booked in a given time window.

Discovers known rooms from reservation history (past year + next 3 months), then checks which are booked in the requested window. Returns rooms with no conflict, each with its numeric id (needed for book_room) and full_name.

Use name_filter to narrow to a specific room or building wing.

Note: room discovery relies on past booking history. Rooms that have never been booked in the past year will not appear in the results even if they are free. If you believe a room is missing, try passing its name (or a fragment) via name_filter, which triggers an additional direct room-name lookup.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
locationYesIndico location/building name (e.g. 'AlbaNova', 'CERN').
dateYesDate to check, YYYY-MM-DD.
from_timeYesStart of desired window, HH:MM (24-hour).
to_timeYesEnd of desired window, HH:MM (24-hour).
name_filterNoOptional room name fragment to narrow the search.
instanceNoNamed Indico instance to query. Use only configured names. If omitted, the server default instance is used.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses that room discovery relies on booking history, mentions the limitation with never-booked rooms, and explains that name_filter triggers an additional direct lookup. This provides good behavioral context beyond a simple list operation.

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 concise yet thorough. It starts with a clear one-line summary, then provides necessary details and a note. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (6 parameters, no annotations, output schema exists), the description is complete. It covers tool behavior, limitations, parameter guidance, and even mentions the output includes id and full_name. No additional context is needed.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3. The description adds value by explaining the name_filter's special behavior (triggers direct lookup), which is not in the schema description. The other parameters are well-described in schema, so the description complements effectively.

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 clearly states the tool's purpose: 'List rooms that are NOT already booked in a given time window.' It distinguishes from siblings like 'book_room' and 'search_rooms' by focusing on availability and mentioning the booking history limitation.

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 explains when to use the tool (to find available rooms) and how to use name_filter. It also highlights a key limitation about rooms never booked, which guides usage. However, it does not explicitly compare to sibling tools like 'discover_rooms' or 'search_rooms'.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cohm/indico-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server