Skip to main content
Glama

Data Baltimore

by io.github.pipeworx-io

Baltimore Layers

baltimore_layers
Read-onlyIdempotent

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

Input Schema

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

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: +[
+  {
+    "service": "crime"
+  },
+  {}
+]
  2. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations already indicate readOnly, openWorld, idempotent, and non-destructive. Description adds return value (layer id + name) and explains dual mode (list services vs layers), enriching transparency.

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?

Very concise: two sentences covering purpose, usage, and output. Front-loaded with core purpose. No wasted words.

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 and no output schema, the description fully explains inputs, output format (layer id + name), and contextual use with baltimore_query.

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

Parameters5/5

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

Single parameter 'service' is fully described in schema (100% coverage). Description adds examples and clarifies behavior when omitted vs provided, adding value beyond 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 clearly states 'List the layers of a Baltimore ArcGIS service (for discovery).' It specifies the verb and resource, and distinguishes from sibling tools like baltimore_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?

Provides explicit guidance: use a short name or full path to list layers, omit to list known services. Also indicates output is for use with baltimore_query, aiding downstream selection.

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

All Data Baltimore 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

A4.1/5.0
Disambiguation2/5

Several tool groups overlap heavily: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route questions to the same catalog; entity_profile, recent_changes, and compare_entities cover overlapping company-data territory; ai_visibility_check and scan_competitor_ai_presence are near-duplicates. Agents would frequently need to read long descriptions to pick the right tool.

Naming Consistency4/5

All tool names use snake_case and mostly follow verb_noun patterns (ask_pipeworx, compare_entities, resolve_entity, validate_claim). Minor inconsistencies exist: generic noun-only names like entity_profile, recent_changes, and bet_research, plus inconsistent prefixes (ask_, baltimore_, polymarket_, pipeworx_, scan_) that group by domain rather than action.

Tool Count3/5

34 tools is on the heavy side for a data-access server, though the scope is broad. Several tools feel tangential to the core data mission (remember/recall/forget, generate_llms_txt, pipeworx_feedback, pipeworx_trending), and the ask_pipeworx family plus the six polymarket_* tools inflate the count with overlapping functionality.

Completeness4/5

The surface covers the domain well: discovery (discover_tools, suggest_questions, baltimore_layers), lookup (ask_pipeworx, baltimore_query/recent), grounded verification (ask_pipeworx_grounded, validate_claim), comparison (compare_entities), profiling (entity_profile), change tracking (recent_changes), and prediction-market analysis. Minor gaps include no direct web search and no Baltimore-specific export/bulk operations, but agents can work around these.

Resources