Skip to main content
Glama

Co Regulation

co_regulation
Read-onlyIdempotent

Get the TEXT of a Colorado administrative regulation (Code of Colorado Regulations, CCR) by citation, with its effective date. "1 CCR 212-3" is the Colorado Marijuana Rules; pass rule="2-245" to read one rule inside it (e.g. change of owner / transfer of ownership), or omit rule to page through the document (rule_index lists the rule numbers). Returns the current version by default, plus filing type, adopted date, Colorado Register publication and the list of earlier effective dates; pass effective_date for an earlier version. Naming only an agency (e.g. "2 CCR 502") returns that agency's document list. Colorado Secretary of State, live, keyless. Statutes are co_statute; this is the regulations.

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": {
      "rule": "2-245",
      "ccr_number": "1 CCR 212-3"
    },
    "name": "co_regulation"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruleNoOptional rule number inside the document, e.g. "2-245" or "1-105". Omit to read from the start of the document.
offsetNoCharacter offset to continue a long text from next_offset.
max_charsNoMax characters of text to return (default 30000, max 100000).
ccr_numberYesCCR citation, e.g. "1 CCR 212-3" (Colorado Marijuana Rules) or "2 CCR 502-1". Volume, agency number, dash, document number.
effective_dateNoOptional. YYYY-MM-DD effective date of an earlier version (listed in archived_effective_dates). Omit for the current version.

Output Schema

NameRequiredDescriptionDefault
ruleNo
textNo
foundNo
titleNo
agencyNo
reasonNo
sourceNo
adoptedNo
messageNo
documentsNo
ccr_numberNo
data_as_ofNo
departmentNo
is_currentNo
rule_indexNo
text_charsNo
filing_typeNo
next_offsetNo
total_charsNo
effective_dateNo
earlier_effective_datesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive, so the safety profile is covered. The description still adds real behavior beyond that: default-to-current-version, the extra metadata returned (filing type, adopted date, Register publication, earlier effective dates), paging via rule_index, and that the source is live and keyless. It does not spell out rate limits or truncation handling beyond max_chars, which keeps it at a 4.

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-loaded with the core action, then progressive detail on parameters and the sibling distinction. Dense but every sentence conveys a calling decision or a behavioral fact; nothing is redundant with the title.

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 five-parameter tool with an output schema, this covers the defaults, the paging path for long documents, the version-selection path, the agency-only edge case, and the sibling boundary. Nothing an agent needs 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 100%, so the baseline is 3, but the description adds meaning beyond the schema: that effective_date values come from the listed archived_effective_dates, that omitting rule pages from the start with rule_index as the index, and that an agency-only citation returns a document list rather than text. That is genuine semantic value on top of already-complete parameter docs.

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?

The description opens with a specific verb and resource ('Get the TEXT of a Colorado administrative regulation ... by citation'), names the citation format, and explicitly distinguishes itself from the statute sibling ('Statutes are co_statute; this is the regulations'). An agent can tell instantly what this returns and how it differs from co_statute and co_regulation_search.

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?

It gives conditional routing in both directions: pass rule="2-245" to read one rule, omit rule to page through the document, pass effective_date for an earlier version, and naming only an agency returns the document list. It also names the alternative tool for statutes.

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.