Skip to main content
Glama

Montgomery Datasets

montgomery_datasets
Read-onlyIdempotent

Search the Montgomery County, MD open-data catalogue (data.montgomerycountymd.gov) for datasets by keyword. Returns dataset names, descriptions, and Socrata resource ids to use with 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": {
      "query": "building permits",
      "_apiKey": "your-data-montgomery-api-key"
    },
    "name": "montgomery_datasets"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax datasets (1-100, default 20).
queryNoKeyword(s).
offsetNoOffset for paging.
_apiKeyNoOptional, your own Socrata app token for higher rate limits. Omit to use the keyless endpoint.

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",
      +    "query": "building permits"
      +  },
      +  {
      +    "_apiKey": "your-data-montgomery-api-key",
      +    "limit": 10,
      +    "query": "crime incidents"
      +  }
      +]
  3. First observed

TDQS

A4.2/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 value beyond that by disclosing what the call returns (dataset names, descriptions, resource ids) and how those ids feed into montgomery_query.

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 tight sentences with no waste. The purpose comes first, and the return contract plus downstream hand-off follow immediately.

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?

There is no output schema, and the description compensates by naming the returned fields and their intended use. For a four-parameter, zero-required discovery tool with full annotation coverage, this is nearly complete; only paging and default-limit behavior are left to the schema.

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 keyword, limit, offset, and the optional _apiKey token are already documented in the schema. The description adds only the notion that matching is by keyword and does not explain paging or rate-limit behavior beyond what the schema states, so 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: search the Montgomery County, MD open-data catalogue for datasets by keyword. It also names the downstream consumer, montgomery_query, which lets an agent distinguish this discovery tool from the query tool 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the correct workflow: search here, then use the returned Socrata resource ids with montgomery_query. That is a clear use context, but it offers no explicit when-not-to-use guidance or exclusions.

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.