Skip to main content
Glama

The Marketing Vault

List standing rules

list_standing_rules
Read-onlyIdempotent

Lists a business's saved standing rules with their ids. Does not use a generation.

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

Input Schema

NameRequiredDescriptionDefault
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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered elsewhere. The added 'Does not use a generation' is genuinely beyond annotations (quota/cost behavior), but it is vague — the term 'generation' is undefined and no other behavior (empty results, ordering) is disclosed.

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 short sentences with the resource and return payload front-loaded, no padding. The trailing sentence is fragmentary and its key term ('generation') is left unglossed, which slightly weakens structure.

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 one-parameter, read-only list tool with no output schema and full schema coverage, the description is close to sufficient. Minor gaps: what a rule record contains and how ids are used downstream.

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% with a single optional uuid described as coming from list_businesses with a default. The description adds only that results are scoped to a business, which the schema already conveys; 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 ('Lists a business's saved standing rules') and adds what is returned ('with their ids'), which is more than a restatement of the name. It does not explicitly contrast with list_saved_outputs or explain why ids matter (for update/delete_standing_rule), so sibling differentiation is only partial.

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 phrase 'Does not use a generation' implies a cost-free context, but the description never states when to call this versus list_saved_outputs, nor that the returned ids feed add/update/delete_standing_rule. Usage is inferable rather than stated.

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