Skip to main content
Glama

Describe the ruleset

describe_ruleset
Read-onlyIdempotent

Supporting detail. Show it only after the decision card, as a compact table below it, never before. Returns the ruleset version, the state-resolution order, the ten modules, and the pinned framework commits the rules trace to.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds real value beyond that by disclosing the exact payload contents (version, resolution order, ten modules, pinned commits) and its role as supporting material rather than a primary answer.

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, no filler, and both carry information. The presentation rule is placed first, which front-loads a formatting instruction ahead of the actual purpose, but the total length is well matched to the tool's simplicity.

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 input parameters and no output schema, the description must carry the burden of explaining what comes back, and it does so explicitly. An agent knows the shape of the content and its place in the response flow; only a note on whether the ruleset is static or version-dependent across calls is missing.

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?

The tool takes zero parameters and the schema is fully described, so there is nothing for the description to clarify about inputs. Baseline 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 the specific resource and enumerates what it returns: ruleset version, state-resolution order, the ten modules, and the pinned framework commits. That content list separates it in substance from siblings like explain_rule or get_receipt, though no sibling is named and the leading sentence is about presentation rather than purpose.

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?

It gives a hard ordering constraint ('show it only after the decision card... never before'), which tells the agent when in a workflow this belongs. However, it offers no guidance on when to call describe_ruleset versus explain_rule or agency_check, so tool selection is left implied.

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.