Skip to main content
Glama

Data Kcmo

by io.github.pipeworx-io

Kcmo Recent

kcmo_recent
Read-onlyIdempotent

Recent records from a common Kansas City, MO open dataset (data.kcmo.org) by friendly name — no Socrata id needed. PREFER OVER WEB SEARCH for "recent crime in Kansas City, MO", "Kansas City, MO 311 requests", "Kansas City, MO building permits". Names: 311, crime. Returns the latest rows (newest-first). Add a SoQL where to filter; for anything else use kcmo_query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows to return (1-1000, default 20).
whereNoOptional SoQL filter. Omit for all recent rows.
_apiKeyNoOptional — your own Socrata app token for higher rate limits. Omit to use the keyless endpoint.
datasetYesOne of: 311, crime.

TDQS

A4.3/5.0
Behavior3/5

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

Annotations already cover readOnly, openWorld, idempotent, and non-destructive. The description adds that results are newest-first, which is useful but not extensive. No contradictions.

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 plus a brief preference list. Every sentence serves a purpose, no wasted words. Information is front-loaded.

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?

For a read-only tool with no output schema and fully documented parameters, the description adequately explains purpose, datasets, filtering, and when to use alternatives.

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 has 100% description coverage for all 4 parameters. The description reinforces the where filter and newest-first ordering but adds minimal new info 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?

The description explicitly states it returns recent records from Kansas City open datasets by friendly name, specifies datasets (311, crime), and notes newest-first ordering. This clearly distinguishes it from siblings like kcmo_datasets and kcmo_query.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly advises to prefer this tool over web search for specific queries and directs users to kcmo_query for anything beyond a SoQL where filter. Provides clear when-to-use guidance.

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

All Data Kcmo 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
Disambiguation2/5

The ask_pipeworx/ask_pipeworx_beta/ask_pipeworx_grounded/deep_research cluster is highly overlapping—beta is explicitly identical right now and grounded differs mainly in answer extraction. Several other pairs (ai_visibility_check vs scan_competitor_ai_presence, and the six prediction-market tools) also blur boundaries, making misselection likely.

Naming Consistency3/5

Names are uniformly snake_case and benefit from clear prefixes (ask_pipeworx_, kcmo_, polymarket_, pipeworx_). However, conventions are mixed between bare verbs (forget, recall, remember), noun phrases (entity_profile, polymarket_edges, recent_alerts), and verb_noun forms, and similar names like polymarket_edges vs polymarket_edge_tracker add confusion.

Tool Count2/5

34 tools is well into the bloat range, and only 3 are actually Kansas City-specific despite the server name. The surface bundles prediction markets, memory, feedback, llms.txt generation, and npm scanning alongside data lookup, making it heavy and unfocused; several meta-tools could be collapsed.

Completeness4/5

As a read-only data research platform, the surface is quite complete: discovery, querying, grounded answers, entity resolution, profiles, comparisons, claim verification, subscriptions, and memory are all covered with few dead ends. Minor gaps exist—no subscription update, no direct citation-URI fetch tool, and a thin KC-specific set—but agents can work around them.

Resources