Skip to main content
Glama

Boston Query

boston_query
Read-onlyIdempotent

Query any City of Boston datastore resource (data.boston.gov, CKAN) by its resource id (a UUID). Supports a free-text q, exact-match filters (field -> value), sort ("field desc"), limit and offset. Use boston_datasets to find a resource id, or boston_recent for the common ones.

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": {
      "sort": "OCCURRED_ON_DATE desc",
      "limit": 100,
      "filters": {
        "district": "B2"
      },
      "resource_id": "b973d8cb-eeb2-4e7e-99da-c92938efc9c0"
    },
    "name": "boston_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoFree-text search across columns.
sortNoSort clause, e.g. "OCCURRED_ON_DATE desc".
limitNoMax rows (default 100, max 1000).
offsetNoRow offset for paging.
filtersNoExact-match filters as a JSON object, e.g. {"district":"B2"}.
resource_idYesCKAN datastore resource id (UUID), e.g. "b973d8cb-eeb2-4e7e-99da-c92938efc9c0".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "filters": {
      +      "district": "B2"
      +    },
      +    "limit": 100,
      +    "resource_id": "b973d8cb-eeb2-4e7e-99da-c92938efc9c0",
      +    "sort": "OCCURRED_ON_DATE desc"
      +  },
      +  {
      +    "limit": 50,
      +    "q": "pothole",
      +    "resource_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
      +  }
      +]
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that the backend is CKAN and that resources are addressed by UUID, which is useful context, but says nothing about return shape, pagination behavior, rate limits or how errors surface for a bad resource id.

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?

Two sentences, zero waste: the core query capability and its addressing requirement come first, then the capability list, then the routing to siblings. No filler or repetition of the title.

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

Completeness3/5

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

The definition is adequate for invocation: what it queries, how it is addressed, which parameters narrow results, and which siblings supply the required id. With no output schema and six parameters including a nested filters object, it should say something about what comes back (rows only, row count, total for paging), which it leaves entirely unstated.

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 description coverage is 100% and every parameter already carries a description plus two worked examples, so the schema carries the load. The description's mention of free-text q, exact-match filters and "field desc" sort restates the schema rather than adding syntax rules, defaults or edge cases beyond it; baseline 3 applies.

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: query any City of Boston datastore resource on data.boston.gov (CKAN), addressed by resource id UUID. It also names the supported query capabilities and the two sibling tools that resolve resource ids, so an agent can distinguish it without opening the schema.

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?

Explicitly routes the agent: use boston_datasets to find a resource id, or boston_recent for the common ones, which tells the agent when to use this tool versus the lookups. It stops short of stating exclusions or prerequisites, such as whether arbitrary CKAN resources outside Boston are supported or whether any dataset is off-limits.

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.