Skip to main content
Glama

get_rule

Read-onlyIdempotent

Get one rule in full, including the exact quote from the law and its official source link. Use it to show proof for a warning.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rule_id": "<rule_id>"
    },
    "name": "get_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
rule_idYesrule_id from a check_legal_risks warning

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is established structurally. The description adds that the response carries the verbatim legal quote and official source link, which is useful, but says nothing about failure modes (invalid or stale rule_id), pagination, or staleness of the citation.

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 short sentences with zero filler and the payload description front-loaded before the usage hint. Nothing is redundant or buried, though it is terse enough that the usage hint reads as an afterthought.

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 lookup with an output schema and full annotation coverage, the description covers what it returns and when to reach for it. The only gap is error behavior when the rule_id is unknown, which is minor at this complexity level.

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% and rule_id already documents 'from a check_legal_risks warning,' so the baseline is 3. The description reinforces the provenance contract with 'Use it to show proof for a warning,' making the dependency on check_legal_risks output explicit, which is a small but real addition.

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 one rule in full') and specifies the payload content: the exact quote from the law plus its official source link. An agent can tell this apart from check_legal_risks (which flags risks) and get_fact_questions 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?

Gives a concrete use case tied to a sibling: 'Use it to show proof for a warning,' i.e. call after check_legal_risks produces a warning needing citation. It does not state when-not to use it or name get_fact_questions as an alternative, so it stops short of full routing guidance.

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.