get_sessionRetrieve a B2match event session route by session ID or URL path, including optional attendee preview pagination.
Fetch a session route. Provide session_id, or path to a session URL. Path alone is enough; session_id is not required when path is set.
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | ||
| event | Yes | B2match event URL, slug/euid, or numeric event id. | |
| session_id | No | ||
| attendees_after | No | ||
| attendees_first | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description usefully adds the path/session_id precedence rule, but says nothing about the paging behavior implied by attendees_first/attendees_after. With annotations carrying the safety burden, a 3 is appropriate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with no waste; the parameter-precedence rule is front-loaded after the purpose statement. Every sentence earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a 5-parameter, read-only tool with no output schema and low schema coverage, the description covers the critical path/session_id decision but omits the attendee-pagination parameters and any note on what is returned. Adequate but with clear gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 20% (just 'event'), so the description must compensate. It clarifies path and session_id as alternatives, covering two of the undocumented parameters, but leaves attendees_after and attendees_first unexplained.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Specific verb+resource ('Fetch a session route') that an agent can distinguish from siblings like get_event and list_session_attendees. 'Route' is slightly jargon-y, but the intent (retrieve one session) is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives invocation guidance on which parameter to supply ('Provide session_id, or path ... Path alone is enough'), which is genuinely useful. However, it offers no when-to-use context relative to alternatives such as get_event or list_session_attendees, so selection guidance is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.