Skip to main content
Glama

Co Titles

co_titles
Read-onlyIdempotent

List the 44 titles of the Colorado Revised Statutes with their official names, Title 18 is the Criminal Code, Title 42 is Vehicles and Traffic, Title 38 is Property, and so on. Keyless. Use when you know the subject but not the title number, before calling co_statute or co_search.

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": {
      "subject": "DUI"
    },
    "name": "co_titles"
  }
}

Input Schema

NameRequiredDescriptionDefault
subjectNoOptional subject to filter by, e.g. "divorce", "DUI", "landlord".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new operational context: "Keyless" signals no credential setup is needed, and the enumeration of the 44 titles conveys the response shape and bounded size. It stops short of describing how the optional subject filter matches, but that is a minor gap.

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?

Two sentences, front-loaded with what the tool returns and followed by the routing guidance. The mid-sentence enumeration of titles is slightly discursive, but every clause carries useful signal and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with rich annotations and a fully documented single parameter, the description covers purpose, scope, and routing to siblings. The only omission is filter behavior (fuzzy vs. exact subject matching) and whether an unfiltered call returns all 44 titles, which is a small residual gap.

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% and the single optional subject parameter is fully documented with examples ("divorce", "DUI", "landlord"). The description's "know the subject but not the title number" frames the parameter's purpose in the workflow, but adds no matching semantics or format details beyond the schema, so the 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 and resource: "List the 44 titles of the Colorado Revised Statutes with their official names." It even previews the content (Title 18 Criminal Code, Title 42 Vehicles, Title 38 Property), so an agent knows exactly what comes back and can distinguish this lookup tool from co_statute and co_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?

Explicit when-to-use: "Use when you know the subject but not the title number, before calling co_statute or co_search." It names the two alternatives and the precondition that selects this tool over them, leaving nothing to inference.

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.