Skip to main content
Glama

Skiddle

by io.github.pipeworx-io

Categories

categories
Read-onlyIdempotent

List Skiddle event category codes (for the search_events category filter).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {}
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds that it returns 'event category codes' and that they are for a filter, providing domain context beyond what annotations offer.

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?

A single, front-loaded sentence with no wasted words. Every part of the description is necessary and efficiently conveys the tool's purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters, no output schema, and clear annotations, the description is fully complete for a simple listing tool. The sibling list includes search_events, making its usage context obvious.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero parameters, so the baseline is 4. The description does not need to add parameter info; it adds value by explaining the tool's output (codes for a filter).

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?

The description uses a specific verb 'List' and identifies the resource 'Skiddle event category codes' with a clear purpose for the 'search_events category filter'. It effectively distinguishes itself from sibling tools like search_events.

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?

The description explicitly states the tool is used for obtaining category codes for search_events, implying when to use it. It does not explicitly state when not to use it, but the context is clear and connects to a sibling tool.

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

All Skiddle toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation3/5

Most tools have clearly distinct roles, but the ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research cluster overlaps heavily as question-answering and research entry points, with ask_pipeworx_beta currently being an exact duplicate of ask_pipeworx. The prediction-market tools are individually differentiated but numerous enough that selecting the right one requires careful reading.

Naming Consistency4/5

The set is predominantly snake_case and mostly readable, with sensible prefixes like ask_, search_, polymarket_, and scan_. However, conventions mix verb-first names (remember, subscribe, validate_claim), noun-style names (categories, event, entity_profile), and adjective-noun names (recent_alerts, recent_changes), so the pattern is not fully uniform.

Tool Count2/5

34 tools is well above the 25-tool threshold where a server starts to feel heavy, and many could be consolidated (7+ prediction-market tools, 4+ overlapping ask/research tools, plus memory and subscription helpers). The breadth is somewhat justified by the Pipeworx data platform, but the surface is still overloaded for a single server.

Completeness4/5

For the broad data/research domain, coverage is strong: lookup, grounded verification, deep research, entity profiles, comparisons, change feeds, tool discovery, memory, and subscription lifecycle all have coherent coverage. Minor gaps exist, such as no explicit tool to read a pipeworx:// citation URI directly and a fairly thin Skiddle events side beyond search/detail/categories.

Resources