Skip to main content
Glama

Co Statute

co_statute
Read-onlyIdempotent

Get the FULL TEXT of a section of the Colorado Revised Statutes (C.R.S.), Colorado state law, by citation. "C.R.S. 18-3-102" is murder in the first degree. Returns the statutory text, the amendment "Source:" history, and cross references. Pass "year" (2000-current, except 2025 which is not yet supported) to get an older edition instead of the current one, e.g. to see how a section read before a given amendment. Keyless. Use for "what does C.R.S. 18-3-102 say", "Colorado landlord security deposit law", or to check a Colorado statute a case 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": {
      "section": "18-3-102"
    },
    "name": "co_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoOptional. A C.R.S. edition year from 2000 through the current year, to retrieve a historical version of the section instead of the current one. Omit for the current edition.
sectionYesSection as cited, e.g. "18-3-102" (murder) or "38-12-103" (security deposits). Title-article-section; the title is the part before the first dash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, open-world safety profile, but the description adds real value beyond them: it discloses the return contents (statutory text, amendment 'Source:' history, cross references), notes the service is keyless, and flags the noteworthy gap that 2025 editions are not yet supported. Pagination, response size, and error behavior for invalid citations are not addressed.

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 core capability, then return contents, then the year parameter, then usage examples — a logical order. It runs somewhat long with multiple quoted example utterances, but each one illustrates a distinct query shape rather than padding.

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?

With no output schema, the description compensates by naming exactly what is returned, and it fully covers both parameters, the historical-edition capability and its one limitation. An agent has everything needed to decide to call it and construct a valid request.

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 would be 3; the description goes further by explaining the intent behind 'year' (retrieving an edition as it read before a given amendment) and by correcting/clarifying the supported range ('2000-current, except 2025'), which the schema's 'through the current year' wording alone would obscure.

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 — 'Get the FULL TEXT of a section of the Colorado Revised Statutes' — with the citation format and a worked example ('C.R.S. 18-3-102' is murder in the first degree). This makes it clearly distinguishable from sibling search tools like co_search and co_regulation_search, which operate differently.

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?

Explicitly frames usage with quoted user phrasings ('what does C.R.S. 18-3-102 say', 'Colorado landlord security deposit law') and the case-checking scenario, plus a clear rule for when to pass 'year' versus omit it. It does not name a sibling to use instead when the user has no citation (e.g., keyword lookup), which keeps it just below a 5.

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.