cpp-espace-mcp

by norm613

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

list-events

Retrieve events with optional filters by location, date range, category, or include related objects.

Instructions

List events with optional filters by location, date range, or category.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list-events"
  }
}

Input Schema

Name	Required	Description
`locationId`	No	Filter by location ID
`startDate`	No	Filter start date (ISO format)
`endDate`	No	Filter end date (ISO format)
`categoryId`	No	Filter by category ID
`include`	No	Comma-separated related objects to include

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 4, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries full burden of disclosure. It mentions 'list' (implying read) but does not state pagination, response format, ordering, or any side effects. For a list tool with no output schema, this is insufficient.

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?

Single sentence covering the core functionality with no unnecessary words. Perfectly concise and front-loaded.

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?

Given 5 optional parameters and no output schema, the description covers the basic purpose but omits behavioral details (pagination, response structure) and usage context, leaving the agent with incomplete information for confident invocation.

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 100%, so parameters are already well-documented. The description summarizes the filter options (location, date range, category) but adds no additional meaning 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 clearly states it lists events with optional filters. While it does not explicitly differentiate from sibling tools like 'get-event' or 'get-event-occurrences', the plural 'list' and filter options imply a batch retrieval, which is distinct from single-event retrieval.

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 guidance on when to use this tool versus alternatives such as 'get-event' for a single event or 'get-event-occurrences' for recurring events. The description lacks any contextual cues about prerequisites or typical use cases.

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