Skip to main content
Glama
Sign In

Oregon Code

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Or Revised Statute

or_revised_statute
Read-onlyIdempotent

Get the FULL TEXT of a section of the Oregon Revised Statutes — Oregon state law — by citation. "ORS 163.115" is second degree murder. Returns the statutory text. Keyless. Use for "what does ORS 163.115 say" or to check an Oregon statute a case relies on.

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": {
      "section": "163.115"
    },
    "name": "or_revised_statute"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesSection as cited, e.g. "163.115" (murder 2) or "813.010" (DUII). Chapter is the part before the dot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already signal read-only, idempotent, non-destructive behavior. The description adds useful context beyond that: it returns full statutory text, requires no key/authentication, and is focused on Oregon state law. This gives the agent a clear picture of what happens when the tool is called.

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?

The description is three focused sentences with no redundancy. The main purpose and full-text payoff are front-loaded, followed by a concrete example and use-case guidance. Every sentence earns its place.

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 single-parameter read-only retrieval tool, the description is nearly complete: it specifies the input format, the return content, the jurisdiction, and the lack of authentication. It could mention error behavior for unrecognized citations, but that is a minor omission given the tool's simplicity.

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%, with the single 'section' parameter explained with format guidance and examples. The description reinforces that the parameter is a citation like 'ORS 163.115' but does not add substantive detail beyond the schema. Baseline 3 is appropriate because the schema carries the burden.

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 immediately states the exact verb and resource: 'Get the FULL TEXT of a section of the Oregon Revised Statutes by citation.' It also gives a concrete example, 'ORS 163.115' is second degree murder, which anchors the tool's domain and distinguishes it clearly from the unrelated sibling tools.

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?

The description provides explicit use cases: 'Use for "what does ORS 163.115 say" or to check an Oregon statute a case relies on.' This tells the agent when to invoke the tool. It does not name exclusions or alternatives, but none of the sibling tools are statute-related, so the lack of an explicit alternative is not a significant gap.

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

All Oregon Code toolsInspect
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.

Resources