Skip to main content
Glama

Plures

Save a standing rule

add_standards_rule

Saves a standing rule for this team's agents, in force at once. Use it only when the user states a preference that should hold from now on, and confirm the wording with them first. One plain sentence.

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": {
      "text": "<text>"
    },
    "name": "add_standards_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesThe rule, as one plain sentence an agent can follow
categoryNoThe kind of work it applies to. Leave out to apply to everything

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the write shape is known. The description usefully adds immediacy ("in force at once") and an interaction obligation (confirm first), but says nothing about whether rules override existing standards, whether duplicates are rejected, or whether the rule can be edited or removed afterward.

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, front-loaded with the effect statement before the usage condition and the format constraint. Every sentence carries information; only "One plain sentence" slightly duplicates the schema's maxLength/length constraints.

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 two parameters, full schema coverage, annotations, and no output schema, the description covers purpose, trigger, confirmation step, and input format. It stops short of explaining what the call returns or how new rules interact with existing ones, which an agent might want before writing a lasting rule.

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%, so both parameters are documented in the schema, giving a baseline of 3. The description still reinforces the required shape with "One plain sentence," which helps an agent avoid multi-clause rules, though it adds nothing about the category parameter's scoping behavior beyond the schema.

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 ("Saves a standing rule") plus its effect domain ("for this team's agents, in force at once"). It is clearly distinct from read-oriented siblings like get_standards, but it never explicitly contrasts with the closest write siblings such as add_standards_example or set_check.

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 supplies a concrete trigger ("the user states a preference that should hold from now on") and a pre-call requirement ("confirm the wording with them first"), which narrows usage well. The word "only" adds an implicit exclusion, though no named alternative is offered for adjacent cases.

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.