Skip to main content
Glama

Data Montgomery

by io.github.pipeworx-io
OverviewDiscussionsAdmin

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.

Input Schema

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

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint. Description adds behavioral details: returns latest rows newest-first, can filter with SoQL where. No contradictions. Could mention pagination or rate limits, but given annotations cover safety, the added context is sufficient.

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?

Compact with three sentences; front-loaded with core function. Every sentence is informative with no redundancy. Uses bold for key instructions and examples in schema.

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 no output schema, the description explains return order. Covers dataset names, filtering, usage guidance, and sibling tool reference. Complete for a simple retrieval tool with good annotations.

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 descriptions cover 100% of parameters. Description adds value by listing the dataset names explicitly (311, crime, permits) and explaining the SoQL where usage. This helps the agent understand the enum values and filtering capability beyond the schema.

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?

Description clearly states the tool retrieves recent records from Montgomery County open datasets by friendly name, and distinguishes from montgomery_query. It specifies exactly which datasets are available (311, crime, permits) and the default behavior (newest-first).

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 says 'PREFER OVER WEB SEARCH' for specific types of queries and provides alternatives: 'for anything else use montgomery_query'. Also advises when to add a SoQL where clause.

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