Ohio Code

Oh Code Search

oh_code_search

Read-onlyIdempotent

Search the Ohio Revised Code BY TOPIC or keyword rather than by section number -- "EDGE certification minority business", "county competitive bidding threshold", "OVI penalties", "landlord security deposit". Covers all chapters of the Revised Code. Returns ranked sections with citation, heading and an opening excerpt; call oh_revised_code with a result's section for the full text. Full-text match, not semantic search. A query with no hits returns found:false. 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": {
      "limit": 5,
      "query": "EDGE certification minority business"
    },
    "name": "oh_code_search"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max results, default 10, max 25.
`query`	Yes	Topic or keywords, e.g. "minority business enterprise certification".

Output Schema

Name	Required	Description
`hint`	No
`count`	No	Results returned
`found`	No	True when at least one section matched
`match`	No	all_words or any_word: which form of the query produced the hits
`query`	No	The query as searched
`reason`	No	On found:false: empty_query, search_unavailable or index_unreachable
`source`	No
`message`	No
`results`	No	Ranked sections
`data_as_of`	No	When the stored chapters were last read from the source

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 3, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, and the description adds genuinely new behavior: ranked results with citation, heading and excerpt; found:false on zero hits; keyless access; and the full-text-not-semantic caveat. These are the details an agent needs to interpret empty or sparse results correctly.

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?

One dense paragraph, front-loaded with the discriminating constraint (topic vs. section number), followed by scope, return shape, follow-up path, and failure mode in order of decision value. No filler sentences.

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 an output schema present, the description need not detail return fields, yet it still summarizes them enough to chain to oh_revised_code. Failure semantics and auth requirements (keyless) are covered, leaving no decision-relevant gap.

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 both parameters are documented, but the description still contributes by demonstrating the natural-language keyword style expected for query and by pointing to the follow-up tool that consumes a returned section. Limit behavior 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?

Names a specific verb and resource (search the Ohio Revised Code) and immediately scopes it as topic/keyword search rather than section-number lookup, which is exactly the distinction from the sibling oh_revised_code. The four concrete query examples make the intended granularity unmistakable.

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?

Explicitly states the selection rule ('BY TOPIC or keyword rather than by section number'), names the complementary tool (oh_revised_code for full text from a result's section), and discloses the matching mode (full-text, not semantic) so the agent knows how to phrase queries and what will not work.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Ohio Code tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.