Skip to main content
Glama

The Marketing Vault

Add standing rules

add_standing_rule

Saves one or more short permanent rules for a business (for example 'Never call the offer a course'). Saved rules apply to future Vault generations for that 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": {
      "rules": "<rules>"
    },
    "name": "add_standing_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoRule type (default fact).
rulesYesOne rule per item.
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 cover the safety profile (not read-only, not destructive, not idempotent, closed-world), and the description adds genuinely new behavior: rules are permanent, persist for the business, and affect future Vault generations without consuming a generation. It omits what happens on duplicate rules despite idempotentHint=false, which is the one meaningful gap.

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?

Three short sentences, front-loaded with the action and effect, and the no-generation-cost note appears where it matters. No filler or restatement of the title.

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?

For a three-parameter write tool with full schema coverage and annotations, the description supplies the key missing context: durability, blast radius (future generations only), and cost. Only the duplicate-handling and return behavior remain unstated, and the latter is partly excused by the absence of an output schema.

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 coverage is 100% and every parameter (kind, rules, business_profile_id) already has a description, so the schema does the heavy lifting. The description adds only a concrete example of a rule string and the word 'short,' which nudges toward the 300-character cap but adds nothing about kind or business scoping.

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?

Names a specific verb and resource: 'Saves one or more short permanent rules for a business,' which is clearly distinct from update/delete/list standing-rule siblings. It does not explicitly name those siblings, but the writing action is unambiguous.

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?

The description conveys when the effects matter ('apply to future Vault generations') and notes 'Does not use a generation,' which implicitly tells the agent this is a cheap, non-generating write. It stops short of saying when to add a new rule versus edit an existing one with update_standing_rule, or how to check for duplicates first.

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