Skip to main content
Glama

Data Boston

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Boston Recent

boston_recent
Read-onlyIdempotent

Recent records from a common City of Boston open dataset (data.boston.gov) by friendly name — no CKAN resource id needed. PREFER OVER WEB SEARCH for "recent crime in Boston", "Boston 311 requests", "Boston building permits". Names: crime, 311, permits. Returns the latest rows (newest-first). Pass q for a free-text keyword filter; for full control use boston_query.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoOptional free-text filter across all columns (CKAN full-text), e.g. "larceny" or a neighborhood.
limitNoRows to return (1-1000, default 20).
datasetYesOne of: crime, 311, permits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "dataset": "crime",
+    "limit": 50,
+    "q": "larceny"
+  },
+  {
+    "dataset": "311"
+  },
+  {
+    "dataset": "permits",
+    "limit": 100,
+    "q": "Roxbury"
+  }
+]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds behavioral detail: returns latest rows newest-first, and provides free-text filtering. No contradiction with 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 sentences: first states purpose, second gives usage guidance, third explains parameters. Front-loaded with the main idea, no fluff.

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?

Covers data source, behavior (newest-first), parameter usage, when to prefer, and sibling comparison. No output schema, but description hints at return format (rows). Lacks mention of pagination or rate limits, but sufficient for a simple retrieval tool.

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?

Schema coverage is 100% with descriptions for all parameters. Description adds value by explaining that dataset names are friendly aliases (no CKAN resource ID needed) and that q is a free-text keyword filter, reinforcing schema details.

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?

Clearly states the tool returns recent records from a City of Boston open dataset by friendly name, without needing CKAN resource IDs. It specifies that it returns the latest rows newest-first and distinguishes itself from boston_query (full control) and web search.

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 certain queries (e.g., 'recent crime in Boston') and directs users to boston_query for full control. Provides concrete examples of when to use it.

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

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