Skip to main content
Glama

Explain a rule

explain_rule
Read-onlyIdempotent

Supporting detail. Show it only after the decision card. Explains one rule by id (for example AC-R-005): what it notices, how it affects the card, and which framework controls it traces to.

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": "explain_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
rule_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile needs no restating. The description adds presentation context (a supporting detail surfaced after the decision card) and the shape of the returned explanation, but says nothing about failure modes such as an unknown or malformed rule id.

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 short sentences with the usage constraint front-loaded ahead of the detail. The opening fragment 'Supporting detail.' is slightly clipped but still orients the reader; there is no filler.

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 must sketch the return value, and it does so by naming the three explanatory components. For a single-parameter read tool with full annotation coverage, that is nearly complete; only error behavior for invalid ids is unaddressed.

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 0%, so the description carries the burden for the single rule_id parameter. It supplies a concrete example format ('for example AC-R-005') and semantics (identifies one rule), but the regex pattern itself lives only in the schema and the description does not explain what happens for ids outside it.

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 uses a specific verb and scope: 'Explains one rule by id' and enumerates the three things returned (what it notices, how it affects the card, which framework controls it traces to). It is clearly narrower than a ruleset-level tool like describe_ruleset, though it never names a sibling explicitly.

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?

It gives a concrete usage condition: 'Show it only after the decision card,' which tells the agent this is a follow-up, drill-down call rather than a primary lookup. It does not address when to skip it or contrast against describe_ruleset, 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.