Skip to main content
Glama

Data Montgomery

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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.

Input Schema

TableJSON 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
    • 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"
+  }
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations indicate readonly, open-world, idempotent, and non-destructive behavior. The description adds that it runs raw SoQL queries with full clause support, mentions optional _apiKey for higher rate limits, and notes a default/max limit of 5000. No contradictions.

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?

The description is extremely concise: two sentences that front-load the action and provide essential context without any wasted words.

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

Completeness5/5

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

Given the tool has 8 parameters, no output schema, but rich annotations, the description sufficiently covers the tool's purpose, how to find resource IDs, supported SoQL clauses, and rate limit considerations. It is complete for an AI agent to invoke correctly.

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?

With 100% schema description coverage, the schema already describes all parameters. The description adds value by explaining _apiKey's purpose (rate limits) and default/max for limit, but does not significantly augment the schema beyond that. Baseline 3 is appropriate.

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?

The description clearly states the tool runs a raw SoQL query against Montgomery County open-data resources, identifies the specific resource using Socrata IDs, and distinguishes from sibling tools like montgomery_datasets and montgomery_recent.

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?

The description explicitly directs users to montgomery_datasets to find a resource ID or montgomery_recent for common ones, providing clear guidance on when to use alternatives. It does not state when not to use this tool, but the context is clear.

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

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