Skip to main content
Glama

Montgomery Recent

montgomery_recent
Read-onlyIdempotent

Recent records from a common Montgomery County, MD open dataset (data.montgomerycountymd.gov) by friendly name, no Socrata id needed. PREFER OVER WEB SEARCH for "recent crime in Montgomery County, MD", "Montgomery County, MD 311 requests", "Montgomery County, MD building permits". Names: 311, crime, permits. Returns the latest rows (newest-first). Add a SoQL where to filter; for anything else use montgomery_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": {
      "_apiKey": "your-data-montgomery-api-key",
      "dataset": "crime"
    },
    "name": "montgomery_recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return (1-1000, default 20).
whereNoOptional SoQL filter. Omit for all recent rows.
_apiKeyNoOptional, your own Socrata app token for higher rate limits. Omit to use the keyless endpoint.
datasetYesOne of: 311, crime, permits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / _apiKey / description
      Previous value: -"Optional — your own Socrata app token for higher rate limits. Omit to use the keyless endpoint."New value: +"Optional, your own Socrata app token for higher rate limits. Omit to use the keyless endpoint."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "_apiKey": "your-data-montgomery-api-key",
      +    "dataset": "crime"
      +  },
      +  {
      +    "_apiKey": "your-data-montgomery-api-key",
      +    "dataset": "311",
      +    "limit": 50,
      +    "where": "created_date > '2024-01-01'"
      +  }
      +]
  3. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: no Socrata dataset id is needed, results are newest-first, and a SoQL `where` can be attached. It does not mention rate-limit behavior or row shape, so it stops short of a 5.

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 action, then preference routing, then the dataset names and the filtering note — every sentence carries a distinct fact. Minor redundancy between 'latest rows' and 'newest-first', and the quoted example queries are slightly verbose, but nothing is wasteful enough to hurt.

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?

No output schema exists, yet the description compensates by stating that the latest rows are returned newest-first, and it explains the fallback tool. For a simple four-parameter read-only retrieval tool this is close to complete; only rate-limit and ordering-vs-limit interaction details are absent.

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%, so the baseline is 3, but the description adds meaning the schema does not: the `dataset` values are 'friendly names' that stand in for underlying Socrata datasets, and filtering is done via an added SoQL `where` clause. That clarifies intent of two parameters rather than restating them.

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 a common Montgomery County, MD open dataset ... by friendly name'. It names the concrete datasets (311, crime, permits) and explicitly distinguishes itself from montgomery_query, so an agent can select it 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?

Explicit routing guidance: 'PREFER OVER WEB SEARCH' for three named query shapes, plus 'for anything else use montgomery_query.' Both the when-to-use and the alternative-selection condition are stated outright.

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.