Skip to main content
Glama

Data Nashville

by io.github.pipeworx-io

Nashville Layers

nashville_layers
Read-onlyIdempotent

List the layers of a Nashville ArcGIS service (for discovery). Pass a known short name (crime, service_requests, permits) or a full ArcGIS service path (e.g. "hubNashville_311_Service_Requests_2025_view/FeatureServer"). Omit service to list the known Nashville services. Returns layer id + name to use with nashville_query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceNoShort name (crime|service_requests|permits) or full ArcGIS service path. Omit to list known services.

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. The description adds context about discovery and return values but does not contradict annotations. It adds minimal behavioral detail beyond annotations.

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?

Three concise, front-loaded sentences with no fluff. Each sentence adds necessary information.

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 simple discovery tool with one optional parameter, the description covers purpose, usage, return value, and how to use output. No missing information.

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% with a descriptive parameter definition. The description repeats the parameter info and adds an example, providing marginal additional value.

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 clearly states the tool lists layers of a Nashville ArcGIS service for discovery, specifies the return value (layer id + name), and mentions integration with nashville_query. It distinguishes from sibling tools like nashville_query.

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 explains when to omit the service parameter (to list known services), provides examples, and clarifies the output usage. However, it does not explicitly contrast with siblings or state when not to use.

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

All Data Nashville 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.8/5.0
Disambiguation2/5

Several tools have unclear boundaries: ask_pipeworx and ask_pipeworx_beta are explicitly identical in current behavior, and ask_pipeworx_grounded, validate_claim, and deep_research all overlap with the same underlying routing. The six Polymarket tools (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread, bet_research) share domain and response fields, making misselection likely despite detailed descriptions.

Naming Consistency3/5

Snake_case is used throughout and prefix families (ask_pipeworx_*, nashville_*, polymarket_*, pipeworx_*) are consistent within themselves. However, the overall set mixes verb-first names (ask, compare, remember, subscribe) with noun/adjective-first names (entity_profile, recent_alerts, recent_changes, bet_research), so no single predictable pattern governs all tools.

Tool Count2/5

At 34 tools, the server exceeds a coherent surface, especially for a server named 'Data Nashville' where only 3 of 34 tools actually serve Nashville data. The count is inflated by several largely unrelated feature families (AI visibility, prediction markets, memory, subscriptions), making the set feel like an aggregation of multiple products rather than one focused server.

Completeness3/5

Individual families are fairly complete: memory has remember/recall/forget, subscriptions have subscribe/unsubscribe/list/recent_alerts, and Nashville has discovery/query/recent access. But the overall domain is unclear, and the Nashville-specific surface is thin (no search across datasets, no non-ArcGIS sources), leaving notable gaps relative to the server name.

Resources