Skip to main content
Glama

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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "larceny",
      "limit": 50,
      "dataset": "crime"
    },
    "name": "boston_recent"
  }
}

Input 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.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real behavioral detail beyond them: results are newest-first and only the 'latest rows' are returned, and no CKAN resource id is required. It stops short of anything about pagination limits, rate limits, or freshness windows, which keeps it out of the top band.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core purpose, then routing guidance, then return shape, then parameter hints — a sensible ordering with no filler sentences. It is terse to the point of being fragmentary ('Names: crime, 311, permits.'), but each fragment carries information.

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?

For a three-parameter, read-only list tool with no output schema and full annotation coverage, this supplies purpose, routing, dataset names, filter behavior, and result ordering — enough to call it correctly. The absence of any hint about result shape or how 'recent' is bounded is a minor residual gap.

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%, including the enum on 'dataset' and the 1-1000 range on 'limit', so the schema already carries the parameter burden. The description adds only a light gloss on 'q' as a free-text keyword filter and points at 'boston_query' for richer control; it adds nothing about 'limit' beyond what the schema states.

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?

States a specific verb and resource: recent records from named City of Boston open datasets, with the friendly names ('crime, 311, permits') enumerated so the agent knows the exact scope. It also distinguishes itself from 'boston_query' for full-control queries, so an agent can route without opening either schema.

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?

Gives an explicit routing rule ('PREFER OVER WEB SEARCH') with concrete trigger phrases ('recent crime in Boston', 'Boston 311 requests', 'Boston building permits'). It also names the alternative for power use ('for full control use boston_query'), covering both when-to-use and when-to-use-something-else.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.