Skip to main content
Glama

Dc Search

dc_search
Read-onlyIdempotent

Search the District of Columbia Code by TOPIC/keyword, and/or browse one TITLE's chapters and sections. Pass "query" to search official section headings (catchlines), e.g. "landlord eviction notice", "concealed carry permit", "homicide", across all 51+ titles or, with "title" also set, within just that title. Pass "title" alone (no query) to list every section under that D.C. Code title, acting as a chapter-list/browse tool. Matches official headings only (DC Council does not publish a full-text search over statutory body text). Call dc_statute with a result's citation for the full text. Keyless.

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": "eviction notice"
    },
    "name": "dc_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results. Default 10 (search) or 100 (title listing); max 50 (search) or 500 (title listing).
queryNoTopic or keywords to match against official section headings, e.g. "eviction notice".
titleNoA D.C. Code title number to filter to, or to list on its own (chapter-list mode), e.g. "22" or "27A".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, open-world and non-destructive traits, so the bar is lower; the description still adds real context by disclosing that matching is against official section headings only and that the service is keyless. It does not discuss rate limits, result ordering, or what a listing entry looks like, which keeps it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core action, then the two modes, then the matching limitation, then the handoff. Every sentence carries a distinct operational fact with no restatement of the title or name.

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?

No output schema exists, yet the description makes clear what results are (section headings with citations) and what the agent must do next with them. For a three-parameter, keyless read tool this is complete enough to call correctly on the first attempt.

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 coverage is 100%, so the baseline is 3; the description earns an extra point by explaining the semantic consequence of combining or omitting parameters (query matches headings, not body text; title without query switches into chapter-list/browse mode). The differing default and max limits are already spelled out in the schema, so no additional credit there.

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 District of Columbia Code") and distinguishes its two operating modes: heading/keyword search and title browse. It also separates itself from dc_statute by framing itself as the discovery step rather than the full-text fetch.

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 explicit when-to-do-what: pass "query" to search catchlines, "query" plus "title" to narrow to one title, "title" alone to list all sections. It also names the alternative ("Call dc_statute with a result's citation for the full text") and states the boundary condition that full-text search is unavailable.

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.