Skip to main content
Glama

Data Baltimore

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Baltimore Recent

baltimore_recent
Read-onlyIdempotent

Recent records from a common Baltimore open dataset (data.baltimorecity.gov / ArcGIS) by friendly name. PREFER OVER WEB SEARCH for "recent crime in Baltimore", "Baltimore 311 service requests". Names: crime, 311. Returns the latest rows (newest-first), epoch dates converted to ISO. Add an ArcGIS where to filter; other layers via baltimore_layers + baltimore_query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoRows to return (1-1000, default 20).
whereNoOptional ArcGIS SQL where, e.g. "OFFENSE='THEFT/OTHER'" or "WARD='2'". Omit for all recent rows.
datasetYesOne of: 311, crime.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "dataset": "crime",
+    "limit": 20
+  },
+  {
+    "dataset": "311",
+    "limit": 50,
+    "where": "WARD='10'"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate read-only and idempotent behavior. The description adds that rows are returned newest-first and epoch dates are converted to ISO, which are useful traits beyond the annotations. 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?

The description is three sentences with no fluff: first sentence defines purpose, second provides usage guidance, third explains behavior and alternatives. Every sentence earns its place.

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

Completeness4/5

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

Given the rich schema and annotations, the description covers key behavioral aspects and sibling tool distinctions. However, it lacks details about the output structure (e.g., columns for crime vs 311). Since there is no output schema, a brief note on return format would improve completeness.

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% and descriptions within schema are detailed. The tool description adds minimal parameter-specific meaning: it reinforces the 'where' parameter as an ArcGIS SQL filter and mentions 'friendly name' for dataset, but mostly repeats schema info. Baseline score is appropriate.

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?

Description explicitly states it returns recent records from Baltimore open datasets by friendly name, with specific examples like crime and 311. It distinguishes from siblings by mentioning 'other layers via baltimore_layers + baltimore_query', clearly differentiating its scope.

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 gives clear positive guidance: 'PREFER OVER WEB SEARCH for recent crime in Baltimore' and similar. It mentions alternatives for other layers. However, it does not explicitly state when not to use this tool, leaving some inferential gap.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources