Skip to main content
Glama

Ok Titles

ok_titles
Read-onlyIdempotent

List all 94 titles of the Oklahoma Statutes with their official names, e.g. Title 21 is Crimes and Punishments, Title 41 is Landlord and Tenant. Routing help for when you know the subject but not the title number, call this or ok_search before guessing a citation. 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": {},
    "name": "ok_titles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds useful context beyond that: it is keyless, it contains exactly 94 titles, and it serves as a citation-avoidance lookup, though it does not describe the response format.

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?

Three short sentences, front-loaded with the core capability and followed by routing guidance. Every sentence adds distinct value with no filler or repetition.

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 zero-parameter lookup with full annotation coverage and no output schema, the description is complete enough to call correctly. It explains what the list contains, gives examples, and tells the agent when to prefer it over guessing a citation.

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?

The tool takes zero parameters, so parameter semantics are inherently trivial. The description correctly does not invent parameter guidance, and the empty input schema is consistent with a no-argument listing tool.

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 states a specific verb and resource: list all 94 titles of the Oklahoma Statutes with official names. Concrete examples (Title 21 = Crimes and Punishments, Title 41 = Landlord and Tenant) make the output shape unmistakable and distinguish it from ok_search and ok_statute.

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 an explicit routing rule: when you know the subject but not the title number, call this or ok_search before guessing a citation. The alternative is named, though the description does not clearly differentiate when to choose this tool versus ok_search.

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.