Skip to main content
Glama

Ok Search

ok_search
Read-onlyIdempotent

Search the Oklahoma Statutes by TOPIC or keyword rather than citation, e.g. "landlord", "concealed carry permit", "DUI per se limit". Real full-text search over statutory body text (not just captions), a query like "landlord" surfaces sections whose heading never says "landlord" (e.g. "Termination of Tenancy", 41 O.S. section 111). Returns matching citations, headings, effective dates, and relevancy. Call ok_statute with a result's citation for the full text. 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": "landlord"
    },
    "name": "ok_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results to return, default 10, max 50.
queryYesTopic or keywords, e.g. "landlord security deposit".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/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, non-destructive behavior, so the safety profile is covered. The description adds real value beyond that: it clarifies the search is over statutory body text rather than captions, explains why a heading-mismatch section still surfaces, lists the return fields, and states the service is keyless. Pagination behavior and ranking mechanics beyond "relevancy" are left implicit.

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 purpose, then supported by a concrete example and an explicit follow-up call. Slightly dense with parenthetical examples, but each sentence carries information an agent needs rather than restating the name or annotations.

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?

There is no output schema, but the description compensates by naming the return fields (citations, headings, effective dates, relevancy) and the downstream call to get full text. For a two-parameter read-only search tool, nothing needed for correct invocation 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 baseline is 3, but the description adds genuine meaning beyond the schema: it tells the agent the query is a topical/keyword phrase, not a citation, and gives example query shapes. The limit parameter is only covered by the schema, which is acceptable given full coverage.

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 ("Search the Oklahoma Statutes") plus a clear scope constraint (by topic/keyword rather than citation), and immediately distinguishes itself from the citation-lookup behavior of ok_statute. The example query and the note about full-text body search vs captions remove any ambiguity about what is searched.

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?

"By TOPIC or keyword rather than citation" tells the agent which input mode selects this tool, and "Call ok_statute with a result's citation for the full text" provides the explicit follow-up alternative. The example queries further anchor when this is the right choice, so both the use case and the handoff path are covered.

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.