Skip to main content
Glama

Montgomery Query

montgomery_query
Read-onlyIdempotent

Run a raw SoQL query against any Montgomery County, MD open-data resource (data.montgomerycountymd.gov) by its Socrata id (8-char like "icn6-v9z3"). Full SoQL: where/select/group/order/limit/offset. Use montgomery_datasets to find a resource id, or montgomery_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": {
      "limit": 100,
      "where": "status = 'Open'",
      "_apiKey": "your-data-montgomery-api-key",
      "resource_id": "icn6-v9z3"
    },
    "name": "montgomery_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNoSoQL $group.
limitNoMax rows (default 100, max 5000).
orderNoSoQL $order.
whereNoSoQL $where filter.
offsetNoRow offset for paging.
selectNoSoQL $select.
_apiKeyNoOptional, your own Socrata app token for higher rate limits. Omit to use the keyless endpoint.
resource_idYesSocrata resource id, e.g. "icn6-v9z3".

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",
      +    "limit": 100,
      +    "resource_id": "icn6-v9z3",
      +    "where": "status = 'Open'"
      +  },
      +  {
      +    "_apiKey": "your-data-montgomery-api-key",
      +    "group": "permit_type",
      +    "order": "count DESC",
      +    "resource_id": "p2c7-bxz5",
      +    "select": "permit_type, count(*) as count"
      +  }
      +]
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so the safety profile is covered. The description adds scope beyond that by saying the query runs against ANY resource on the portal, which justifies the open-world flag. It doesn't discuss error behavior for invalid SoQL or resource ids, which is the main remaining gap.

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 short sentences, front-loaded with the core action, then the capability surface, then the sibling routing. No filler and nothing buried.

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 an 8-parameter query tool with full schema coverage and no output schema, the description covers what the tool does and how to obtain a resource id. It could say a word about the returned shape or paging behavior beyond offset, but the schema already carries limits and paging.

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%, so every parameter is already documented, including the api-key rate-limit note and the 5000-row cap. The description's mention of where/select/group/order/limit/offset restates the schema's SoQL clause parameters rather than adding new meaning, so the 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: run a raw SoQL query against a named Socrata open-data portal, addressed by resource id. It also gives the id format (8-char, e.g. "icn6-v9z3") and enumerates the supported SoQL clauses, so an agent knows exactly what capability this exposes.

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 routes the agent to alternatives with conditions: use montgomery_datasets to discover a resource id, or montgomery_recent for the common datasets. That is a clear when-to-use-this vs when-to-use-sibling split.

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.