evand-mcp

List Evand categories

list_categories

Read-onlyIdempotent

Find Evand event categories and subcategories with slugs, parent categories, and event counts, then filter event searches by slug or title.

Instructions

List Evand event categories and subcategories with their slugs, parent categories and event counts. Use the slug or title as the category filter in search_events.

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_categories"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum categories to return, 1-300. Default 100.
`query`	No	Optional case-insensitive filter on category title, slug or parent.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 13, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds useful behavioral context beyond that by enumerating what comes back (slugs, parents, event counts) in the absence of an output schema, though it says nothing about pagination or ordering.

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?

Two sentences, zero waste, with the returned content front-loaded before the downstream usage note. Nothing repeats the title or the annotations.

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?

A simple two-parameter read tool whose safety is covered by annotations and whose parameters are fully described in the schema. The return fields are sketched in the description since no output schema exists, which is enough to call it correctly, though the full record shape (e.g. category IDs, nesting) remains unspecified.

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 limit and query are fully documented in the schema, making 3 the baseline. The description's note that slug or title work as filters implicitly frames the query parameter's usefulness, but adds no format or syntax detail beyond the 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?

States a specific verb and resource ("List Evand event categories and subcategories") and names the payload fields it returns (slugs, parent categories, event counts). Combined with the mention of search_events, an agent can tell this is the taxonomy-discovery tool rather than an event search.

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?

Explicitly tells the agent the downstream use: "Use the slug or title as the category filter in search_events." That gives a clear use case and workflow handoff, though it doesn't state when not to call it or contrast it with the other list_* sibling (list_cities).

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

Deploy Server