eventGet a single Funcheap event by numeric post id or slug, with full cleaned body text (date/venue/price details live in the text).
| Name | Required | Description | Default |
|---|---|---|---|
| id | No | Numeric WordPress post id, e.g. 1624543. | |
| slug | No | Post slug from an event URL, e.g. "fantasia-1940-35mm-live-organ-concert-paramount-theatre-oakland". |
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "id": 1624543
+ },
+ {
+ "slug": "fantasia-1940-35mm-live-organ-concert-paramount-theatre-oakland"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds context about the output: 'full cleaned body text (date/venue/price details live in the text)', which is useful beyond 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that front-loads the purpose and identifier methods, with no extraneous information.
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?
Given no output schema, the description hints at response contents (cleaned body text with date/venue/price). However, it lacks information about error handling or what happens if no event matches. Overall adequate for a simple retrieval tool.
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 coverage is 100% with descriptive parameter comments. The description does not add significant new meaning beyond what the schema provides, so baseline score of 3 is appropriate.
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?
The description uses a specific verb ('Get') and resource ('single Funcheap event'), clearly stating the two identification methods: numeric post id or slug. This distinguishes it from sibling tools like 'search_events' which likely returns multiple events.
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?
The description implies usage when you have an id or slug, but does not explicitly state when to use this tool versus alternatives like 'search_events'. No guidance on choosing between id and slug or when to avoid using the tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.