Skip to main content
Glama

Ri General Law

ri_general_law
Read-onlyIdempotent

Get the FULL TEXT of a section of the Rhode Island General Laws, Rhode Island state law, by citation. "R.I. Gen. Laws 11-23-1" is murder. Returns the statutory text. Keyless. Use for "what does Rhode Island General Laws 11-23-1 say" or to check an RI 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": "11-23-1"
    },
    "name": "ri_general_law"
  }
}

Input Schema

NameRequiredDescriptionDefault
sectionYesSection as cited, e.g. "11-23-1" (murder) or "31-27-2" (DUI). Title-chapter-section.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world, non-destructive. The description adds genuinely non-redundant facts: the tool is 'Keyless' (no credential setup required) and returns the statutory text in full rather than a summary. It stops short of saying what happens when a citation is invalid or the section does not exist.

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 verb and resource, then examples, then usage — everything an agent needs in roughly three sentences. 'Keyless' is a fragment that reads slightly out of place, but it carries real information and costs almost no space.

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 retrieval tool with full schema coverage and rich annotations, the description covers purpose, input format, and return content. No output schema exists, yet the description explicitly states the return is the statutory text, which is sufficient; only error/not-found behavior is unaddressed.

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 the baseline is 3, but the description earns above baseline by showing how a real-world citation ('R.I. Gen. Laws 11-23-1') maps onto the bare 'section' string the parameter expects. That normalization guidance is the main practical failure mode for this tool and is addressed directly.

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 — 'Get the FULL TEXT of a section of the Rhode Island General Laws' — constrained by citation. The concrete example ('R.I. Gen. Laws 11-23-1' is murder) leaves no ambiguity about what is returned, and no sibling tool in the catalog overlaps with this retrieval.

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?

Gives two explicit invocation contexts: answering 'what does Rhode Island General Laws 11-23-1 say' and checking a statute a case relies on. There are no exclusions or named alternatives, but no sibling here performs statutory lookup, so the absence of routing language is not a practical gap.

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.