categoriesList Funcheap categories (slug, name, count) — broader groupings like neighborhoods, "fairs-festivals", "kids-families". Sorted by usage.
| Name | Required | Description | Default |
|---|---|---|---|
| query | No | Optional search to find matching categories. | |
| per_page | No | How many to return (1-50, default 40). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds 'Sorted by usage', which is behavioral info not in annotations, and provides example category values, enriching transparency without contradiction.
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?
Single sentence with clear purpose, examples, and sorting info. No redundant words or unnecessary details. Front-loaded and efficient.
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 two optional parameters, no output schema, and rich annotations, the description adequately conveys the return fields (slug, name, count) and sorting. Sufficient for a simple listing 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 both parameters described. The description adds an example query ('neighborhood') but no additional semantic detail beyond the schema. Baseline 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 clearly states the tool lists Funcheap categories with specific fields (slug, name, count), provides examples like 'neighborhoods' and 'fairs-festivals', and mentions sorting by usage. It distinguishes from siblings like 'tags' by focusing on broader groupings.
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 for retrieving category lists but does not explicitly state when to use this tool vs alternatives like 'tags' or 'search_events'. No when-not-to-use or exclusion criteria are provided.
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.
Most tools are distinct (event search, subscriptions, memory, Polymarket arbitrage, data lookups), but ai_visibility_check, scan_competitor_ai_presence, bet_research, polymarket_edges, and polymarket_arbitrage have overlapping purposes around competitive research and prediction-market edge-finding. The detailed descriptions disambiguate them, though an agent could confuse polymarket_edges with polymarket_arbitrage.
Tool names are mostly descriptive and consistent: search_events, event, categories, tags are aligned; ask_pipeworx, compare_entities, entity_profile follow a similar pattern. However, polymarket_* tools have an odd mix of `polymarket_arbitrage`, `polymarket_fill_risk`, and `polymarket_edge_tracker`, and discover_tools/recent_alerts/recent_changes are consistent, mostly. Naming is quite consistent overall with minor deviations.
At 35 tools, the count is heavier than typical MCP servers, but it reflects a broad service (Funcheap data + Pipeworx data platform + pred markets). Still, plenty of tools serve the same primary purpose (polymarket_, ask_pipeworx variants) so some pruning would improve the surface.
The surface appears complete for its domain: search/retrieve events, category/tag navigation, memory, subscriptions (create/list/cancel/pull), data lookups, entity resolution, comparisons, profiles, edge scanning, and feedback. Minor gaps include no direct 'update' on events (but events are static), and no pricing fetch tool separate from event text, though body text covers it.