Skip to main content
Glama

Secure Autonomous Register

Find rules

find_rules
Read-onlyIdempotent

Regulations and standards that bear on autonomous systems, filtered by keyword, jurisdiction (e.g. 'European Union', 'United States', 'California'), or control ID. Each lists the controls it maps to and how strongly (required, implied, recommended, proposed).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results to return, from 1 to 50. Default 10.
queryNoKeywords that must all appear in the rule's title, summary or issuing body, such as 'crash reporting' or 'incident notification'.
controlNoKeep only rules that map to this control. A control ID such as C-V1; list_controls gives every ID.
jurisdictionNoKeep only rules from one place, matched as part of the name: 'European Union', 'United States', 'California', 'Japan'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / control / description
      Added value: +"Keep only rules that map to this control. A control ID such as C-V1; list_controls gives every ID."
    • addedInput schema / properties / jurisdiction / description
      Added value: +"Keep only rules from one place, matched as part of the name: 'European Union', 'United States', 'California', 'Japan'."
    • addedInput schema / properties / limit / description
      Added value: +"How many results to return, from 1 to 50. Default 10."
    • addedInput schema / properties / query / description
      Added value: +"Keywords that must all appear in the rule's title, summary or issuing body, such as 'crash reporting' or 'incident notification'."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is fully covered. The description's main added value is the return shape: each rule lists mapped controls with a strength label (required, implied, recommended, proposed), which is genuinely useful since no output schema exists. It stops short of describing ordering, pagination, or what an empty result means.

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?

Two sentences, front-loaded with the resource and filters, then the return content. Nothing is redundant, though the second sentence about mapping strength could be read as return-value detail that an output schema would normally carry.

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 simple read-only search with fully documented parameters and annotations covering safety, the definition covers what the tool finds, how it can be filtered, and what results contain. Missing only minor operational details like result ordering or behavior on zero matches.

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%, so all four parameters are already documented with examples and the limit range. The description restates the filter dimensions and adds the jurisdiction examples, but contributes no syntax or matching behavior beyond what the schema provides. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource ('regulations and standards that bear on autonomous systems') and the three filter dimensions (keyword, jurisdiction, control ID), which is clear enough for an agent to recognize a filtered search tool. It does not explicitly contrast itself with siblings like list_controls or get_control, but the resource type alone makes it distinguishable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Filter dimensions are enumerated, which implies when the tool is useful, but there is no explicit guidance on when to choose this over lookups like get_control or list_controls, nor on prerequisites or exclusions. Usage is implied rather than stated.

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.

Resources