Skip to main content
Glama

The Marketing Vault

Edit a standing rule

update_standing_rule
DestructiveIdempotent

Replaces the wording of one saved standing rule for a business. Does not use a generation.

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": "<rule>",
      "new_rule": "<new_rule>"
    },
    "name": "update_standing_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruleYesThe current rule text exactly as saved (case and spacing ignored), or the rule id from list_standing_rules.
new_ruleYesThe replacement rule text.
business_profile_idNoBusiness id from list_businesses. Defaults to the default Business.

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 destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description still adds real value by clarifying the operation is a full wording replacement (not an append or merge) and that it consumes no generation, a cost trait absent from the annotations. It omits what happens when the target rule cannot be matched, but the core behavioral picture is sound.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the operation and followed by the one non-obvious side effect. Nothing is redundant or padded.

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 three fully documented parameters, no output schema, and annotations covering mutation semantics, the description covers what an agent needs to select and call it. It could say more about failure behavior for an unmatched rule, but nothing essential is missing.

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 100%, and the schema itself explains that 'rule' accepts either the exact saved text or an id from list_standing_rules, and that business_profile_id defaults to the default Business. The description adds no meaning beyond that, so the baseline 3 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?

States a specific verb and resource: 'Replaces the wording of one saved standing rule for a business.' The word 'Replaces' plus 'wording' separates it from add_standing_rule and delete_standing_rule without naming them. It stops short of an explicit sibling comparison, so it is clear but not maximally differentiated.

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?

Usage is only implied: edit an existing rule's text rather than create or remove one. There is no explicit statement of when to prefer add_standing_rule or delete_standing_rule, and no preconditions such as the rule having to exist already. The 'Does not use a generation' sentence gives a useful cost signal but is not 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.

Resources