Skip to main content
Glama

rules

Retrieve shared guidance for multi-agent AI coding workflows: get the core layer or all entries by default, and topic-specific guidance when a topic is provided.

Instructions

The shared rules: the core layer (or all rules when nothing is layered); with topic, that topic's rules.

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

Input Schema

NameRequiredDescriptionDefault
topicNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.11

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose conditional behavior around layering and topic filtering, but it does not explicitly state that this is a read-only retrieval operation or describe any permissions, side effects, or limitations.

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?

The definition is compact and front-loads the resource and topic behavior. However, the dense parenthetical and undefined layering terminology reduce clarity despite the efficient length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple and has an output schema, so return values need not be explained in depth. Still, the description leaves key context undefined: what a "layer" is, whether the operation is read-only, and how topic values are interpreted.

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 0%, so the description must compensate for the single undocumented parameter. It meaningfully explains that supplying topic returns that topic's rules, while omitting topic affects whether the core layer or all rules are returned; it could still say more about accepted topic values.

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

Purpose3/5

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

The description identifies the resource as shared rules and explains that a topic narrows the result, but it never uses an explicit retrieval verb and relies on undefined jargon like "core layer" and "layered." It is distinguishable from rule_add by implication, not by an explicit statement.

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

Usage Guidelines2/5

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

The phrase "with topic, that topic's rules" describes parameter behavior rather than when to use this tool versus alternatives such as rule_add or claim. There is no explicit when-to-use or when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools