Skip to main content
Glama

rule_add

Add a shared When/Do/Not rule with an enforcement path, judgment-only reason, or planned check and size to standardize agent behavior across projects.

Instructions

Add a shared rule in the When/Do/Not shape. Needs enforced_by (paths), judgment_only (why no code can), or planned (the check to write) with size S, M or L.

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": {
      "agent": "<agent>",
      "when": "<when>",
      "do": "<do>",
      "topic": "<topic>",
      "reason": "<reason>"
    },
    "name": "rule_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
doYes
not_No
sizeNo
whenYes
agentYes
topicYes
reasonYes
plannedNo
projectNo
replacesNo
enforced_byNo
judgment_onlyNo

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 the enforcement taxonomy and the S/M/L sizing dimension, which is genuine context. However, it says nothing about persistence scope (shared with whom), overwrite/dedup behavior, or the effect of the undocumented replaces parameter.

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 tight sentences with no filler, and the core action is front-loaded ahead of the field constraints. The trailing "with size S, M or L" clause is slightly tacked on but still earns its place by enumerating the allowed values.

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

Completeness2/5

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

For a 12-parameter mutation tool with zero annotation coverage, the description is thin: it omits required fields like agent, topic, and reason, and never describes write semantics or what "shared" implies. The existing output schema covers return values, but the input-side gaps remain substantial.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 12 parameters, so the description must compensate and only partly does. It explains enforced_by, judgment_only, planned, and size, but leaves agent, topic, and reason — three of the five required parameters — as well as project and replaces entirely undefined.

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 gives a specific verb and resource ("Add a shared rule") and names the expected content shape (When/Do/Not), so an agent knows exactly what gets created. It does not differentiate itself from the sibling "rules" tool or explain how this differs from "claim", leaving selection partly to inference.

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 states a real precondition: the rule must be classified via enforced_by, judgment_only, or planned, which tells the agent what is required before calling. It never says when to use this versus reading existing rules or filing a claim, and it gives no exclusion or prerequisite guidance beyond that one-of-three requirement.

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