Skip to main content
Glama

Maple Minute

Stop a yearly add-on

remove_addon
Destructive

Stop a yearly add-on at the end of the year already paid (no refund). For the office address, use the company page, which collects the new address.

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": {
      "id": "<id>",
      "addon": "<addon>"
    },
    "name": "remove_addon"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCompany id like MM-12, from list_companies.
addonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real behavioral detail: the add-on is not terminated immediately, it runs to the end of the paid year, and no refund is issued. That is exactly the kind of consequence information an agent needs before triggering a destructive call. Auth requirements and reversibility are not covered.

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 first sentence is tight and front-loaded with the key fact (no refund, end-of-year effect). The second sentence about the office address is confusing in a cancellation tool and reads as stray guidance, consuming space without helping the agent invoke remove_addon correctly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter destructive mutation with no output schema, the description covers the core consequence (no refund, deferred termination) but omits whether the change can be undone, whether confirmation is needed, and what a successful response looks like. Combined with the undocumented enum, it is adequate rather than complete.

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 only 50%: the id parameter is documented in the schema (MM-12 format, sourced from list_companies), while the addon enum values plan/phone/attorney carry no explanation anywhere. The description's phrase "yearly add-on" contextualizes the enum as yearly-billed add-ons, which adds some meaning, but it never explains the individual enum choices. Baseline 3 fits.

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?

"Stop a yearly add-on" pairs a specific verb with a specific resource, and the parenthetical "(no refund)" pins down the exact semantics of the operation. It implicitly contrasts with the add_addon sibling, but never names or distinguishes itself from alternatives explicitly, and the second sentence shifts to an unrelated address topic.

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 supplies a usable timing rule: the stop takes effect at the end of the year already paid, which tells the agent when this tool is the appropriate action. It gives no explicit exclusions or alternatives (e.g., use add_addon to re-enable, or what to do mid-term), so usage is implied rather than spelled out.

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