Skip to main content
Glama

Dc Statute

dc_statute
Read-onlyIdempotent

Get the FULL TEXT of a section of the District of Columbia Code (D.C. Code), DC statutes, by citation. "22-2101" is murder in the first degree; "42-3505.01" covers eviction notice requirements. Accepts natural forms: "22-2101", "D.C. Code section 22-2101", "DC Code 22-2101". Returns the current statutory text, the official heading, disposition (in force / repealed / transferred / reserved), legislative History annotations, Prior Codifications, and Cross References. The DC Council's own GitHub source (DCCouncil/law-xml-codified, public domain) publishes the CURRENT codified text only, a prior (pre-amendment) version's exact text is not available through this source; this tool says so rather than guessing. Keyless. Use for "what does D.C. Code 22-2101 say" or to check a DC statute a case or lease relies on.

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": {
      "citation": "22-2101"
    },
    "name": "dc_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
citationYesSection citation, title-section, e.g. "22-2101" (murder in the first degree) or "42-3505.01" (eviction notice). The title may carry a letter suffix (e.g. "27A-101").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, it discloses the upstream source (DCCouncil/law-xml-codified, public domain), the keyless access model, the exact response contents (statutory text, official heading, disposition states, history annotations, prior codifications, cross references), and the hard limitation that superseded text is unavailable and the tool reports this rather than guessing. That is unusually rich disclosure for a read tool.

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?

The core purpose and the citation examples are front-loaded, and each subsequent sentence carries distinct information (return fields, source provenance, the prior-version caveat, use cases). It is dense but not padded; the long enumerated return-field sentence is the only mildly heavy passage.

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 single-parameter, no-output-schema lookup tool with strong annotations, the description covers input formats, returned data, data provenance, and the one failure mode an agent would otherwise misjudge (unavailable superseded text). Nothing needed to invoke it correctly is missing.

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 already 100%, so the baseline is 3, but the description adds genuine value by listing accepted natural citation forms ("22-2101", "D.C. Code section 22-2101", "DC Code 22-2101"), which the schema does not spell out. It stops short of describing normalization or fallback behavior when a citation is malformed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource ("Get the FULL TEXT of a section of the District of Columbia Code") and grounds it with concrete citations such as "22-2101" is murder and "42-3505.01" covers eviction notice. It makes the citation-lookup scope unambiguous, though it never names the sibling dc_search or explicitly contrasts search-by-topic with fetch-by-citation.

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?

It gives an explicit trigger ("Use for 'what does D.C. Code 22-2101 say' or to check a DC statute a case or lease relies on") and states a limitation that the source publishes only current codified text, so prior pre-amendment versions cannot be retrieved. This is clear when-to-use guidance with a built-in exclusion, but no sibling alternative is named for the prior-version case.

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.