Skip to main content
Glama

Co Search

co_search
Read-onlyIdempotent

Search the Colorado Revised Statutes GENERAL INDEX by topic and get back matching index entries with their C.R.S. citations, e.g. "landlord", "security deposit", "concealed handgun", "driving under the influence". This is a real subject-index search, not just a title list: it finds the specific section(s) a plain-English topic maps to so you can pass them to co_statute. Works best with a SHORT topic (1-3 words), the index is a nested tree (a topic heading followed by indented sub-entries that do not repeat the heading word), matched here within a small window of nearby lines, so a long compound phrase can miss or pick up a loosely related neighbor. 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": "security deposit"
    },
    "name": "co_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return (default 15, max 50).
queryYesTopic to search for, e.g. "landlord", "security deposit", "concealed handgun". Short phrases work best.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

The annotations already cover read-only, idempotent, open-world, non-destructive behavior, and the description adds genuinely new context: the index is a nested tree, matching happens within a small window of nearby lines, sub-entries do not repeat the heading word, and long phrases can miss or pull in loose neighbors. It also states 'Keyless', which tells the agent no auth is required.

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 co_statute hand-off are front-loaded, and the examples are immediately useful. The middle section is one long run-on sentence about tree/window matching that could be split for readability, but no sentence is filler.

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 still explains what comes back (matching index entries plus citations) and what to do with it. Query limitations, matching mechanics, and keyless access are all covered for a two-parameter lookup tool.

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 baseline is 3, but the description adds the reasoning behind the query format: why 1-3 word topics work and why long compound phrases fail given window-based matching. The limit parameter is left entirely to the schema, which is acceptable.

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 names a specific verb (Search), a specific resource (the Colorado Revised Statutes GENERAL INDEX), and the return shape (matching index entries with their C.R.S. citations). It also distinguishes itself from co_statute by saying results are meant to be passed to that tool.

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 concrete query-shape guidance ('SHORT topic (1-3 words)') and names the downstream tool co_statute as the next step, plus a warning about long compound phrases. It does not explicitly contrast with other statutory search tools such as co_titles or search_within, so the routing guidance is clear but not exhaustive.

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.