Skip to main content
Glama

Accept suggestions

purch_accept_suggestions
Destructive

Confirm what standing rules suggest, in one reasoned act: every waiting row, or one rule's rows, minus any the person says are not part of it. This is a review act, so it follows the person's confirmation, never the rule alone. Show them the rows first (purch_rules lists each rule with the rows it is suggesting for), and leave out any row they say does not belong with except. The reason is their confirmation. Effects: status and category recorded on every row accepted.

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": {
      "reason": "<reason>"
    },
    "name": "purch_accept_suggestions"
  }
}

Input Schema

NameRequiredDescriptionDefault
exceptNoRows to leave unreviewed, comma separated (T-0012, T-0015).
reasonYesWhy: typically "confirmed by the person" plus anything they said.
rule_idNoOnly this rule's suggestions, e.g. RL-0001. Omit for every waiting row.

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, idempotentHint=false and readOnlyHint=false, so the safety profile is known. The description still adds value by stating the concrete effect ('status and category recorded on every row accepted') and the review-act requirement. It does not say whether the write is reversible or what happens to rows excluded via 'except', which is the remaining gap for a destructive tool.

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

Conciseness3/5

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

The scope statement is front-loaded, which is good, but the text is padded with framing sentences ('in one reasoned act', 'This is a review act...') and closes by restating that the reason is the person's confirmation, which was already implied.

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 3-parameter tool with an output-schema-free interface and clear annotations, the definition covers prerequisites, scoping, exclusions and effects well. It could still say what the agent receives back (e.g. count of rows accepted) or how partial/conflicting rows are handled.

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%, so the baseline is 3. The prose restates the meaning of each parameter (rule_id scoping, except for disputed rows, reason as the person's confirmation) but adds little beyond the schema's own descriptions.

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 action (confirm) and resource (rules' suggested rows), and covers both scopes: 'every waiting row, or one rule's rows'. It also implicitly distinguishes itself from purch_rules, which only lists suggestions, so an agent can tell the two apart. The wording 'one reasoned act' is ornamental rather than additive.

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 explicitly says to show the rows first via purch_rules and to leave out disputed rows with 'except', and it frames the tool as following the person's confirmation rather than the rule. That is clear when-to-use guidance; what's missing is any stated precondition failure behavior or a note on when not to accept in bulk.

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.