Skip to main content
Glama

Dc Recent

dc_recent
Read-onlyIdempotent

Recent records from a common Washington, DC open dataset (opendata.dc.gov / ArcGIS) by friendly name, no service ids needed. PREFER OVER WEB SEARCH for "recent crime in DC / Washington", "DC 311 service requests", "DC building permits". Names: crime, 311, permits. Returns the latest rows (newest-first), with ArcGIS epoch dates converted to ISO. Add an ArcGIS where to filter; for other layers use dc_layers + dc_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": {
      "limit": 20,
      "dataset": "crime"
    },
    "name": "dc_recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return (1-1000, default 20).
whereNoOptional ArcGIS SQL where, e.g. "OFFENSE='THEFT/OTHER'" or "WARD='2'". Omit for all recent rows.
datasetYesOne of: crime, 311, permits.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "dataset": "crime",
      +    "limit": 20
      +  },
      +  {
      +    "dataset": "311",
      +    "limit": 10,
      +    "where": "WARD='2'"
      +  },
      +  {
      +    "dataset": "permits"
      +  }
      +]
  2. 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 readOnly, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds behavior beyond them: results are newest-first, ArcGIS epoch dates are converted to ISO, and rows are 'latest' — real return-shape context an agent would otherwise have to guess. It doesn't mention rate limits or failure modes, keeping it 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 highest-value routing signal ('PREFER OVER WEB SEARCH') and packs purpose, names, output shape, and the filter mechanism into a few dense clauses with no filler. It is a single run-on block, which slightly hurts scanability, so a 4 rather than 5.

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?

For a 3-parameter, read-only dataset fetcher with no output schema, the description covers what the tool returns (latest rows, newest-first, ISO dates) and how to narrow results (ArcGIS where) plus where to go for non-curated layers. Nothing an agent needs to call it correctly is missing.

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 all three parameters (limit, where, dataset) are already documented with examples, including the enum values. The description restates the friendly-name list and that a `where` filters, but adds little syntax or semantics the schema doesn't already carry; 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+resource (return recent rows from DC open datasets like opendata.dc.gov/ArcGIS) and enumerates the three supported friendly names (crime, 311, permits). It explicitly distinguishes itself from dc_layers/dc_query by noting those are for 'other layers', so an agent can select without opening schemas.

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?

Gives an explicit routing rule: 'PREFER OVER WEB SEARCH' with concrete query phrasings (recent crime in DC, DC 311 requests, DC building permits), plus a fallback path ('for other layers use dc_layers + dc_query'). Both the when-to-use and the when-to-use-something-else conditions are stated.

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.