Skip to main content
Glama

Reg Rin

reg_rin
Read-onlyIdempotent

Full detail for one Regulation Identifier Number (RIN), across EVERY Unified Agenda edition it has appeared in, proving the rule's history rather than just its latest status. Returns the abstract, agency, and one entry per edition showing how rule_stage, rin_status, and priority_category changed over time. Answers "what is RIN 2060-AV62 about", "history of this rulemaking", "has this rule stalled or progressed".

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": {
      "rin": "2060-AV62"
    },
    "name": "reg_rin"
  }
}

Input Schema

NameRequiredDescriptionDefault
rinYesThe RIN, e.g. "2060-AV62" (format AAAA-Bnnn, 4-char agency code, letter, 3 digits/letters).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / rin / description
      Previous value: -"The RIN, e.g. \"2060-AV62\" (format AAAA-Bnnn — 4-char agency code, letter, 3 digits/letters)."New value: +"The RIN, e.g. \"2060-AV62\" (format AAAA-Bnnn, 4-char agency code, letter, 3 digits/letters)."
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real value by disclosing the return shape: abstract, agency, and one entry per edition tracking rule_stage, rin_status and priority_category over time. It stops short of noting edition coverage gaps, result size, or whether all historical editions are always present.

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?

Three sentences, front-loaded with what it returns and the history-vs-latest distinction, then the field-level detail, then query examples. Dense and mostly waste-free; the acronym expansion could be trimmed since the schema example already conveys the format.

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?

With no output schema, the description carries the burden of describing returns and does so adequately for a single-parameter lookup, naming the fields per edition. Minor gaps remain around result volume and how editions with missing stages are represented, but nothing essential to correct invocation is absent.

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 coverage is 100% and the single parameter already documents the AAAA-Bnnn format with an example, so the baseline is 3. The description contributes only the expansion of the acronym (Regulation Identifier Number) and no additional constraints or edge-case behavior for the rin value.

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 (full detail for one RIN) plus an explicit scope distinction: 'across EVERY Unified Agenda edition it has appeared in, proving the rule's history rather than just its latest status.' That contrast against a latest-status lookup lets an agent separate it from the agenda/search siblings without opening any schema.

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?

Usage is anchored by three concrete example questions ('what is RIN 2060-AV62 about', 'history of this rulemaking', 'has this rule stalled or progressed') that map cleanly onto when to call it. No explicit exclusions or named alternatives are given, so an agent must infer that the agenda/search tools are for other query shapes.

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.