Skip to main content
Glama

Maple Minute

Add a yearly add-on

add_addon

Turn on a yearly add-on for a paid company: plan (filing plan), phone (company phone number), office (virtual office, where available) or attorney (Maple Minute as the BC attorney, for a company registered in BC with its office elsewhere). Returns a checkout_url for a person to pay.

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": "add_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

A4.1/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false and destructiveHint=false; the description adds the crucial behavioral fact that this does not immediately activate the addon but returns a checkout_url for a person to pay. It also discloses availability constraints per addon type (office regional availability, attorney BC-registration requirement), which is real context beyond the structured fields.

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?

A single front-loaded sentence enumerating the options, followed by one sentence on the return value; almost no wasted wording. Slightly dense parenthetical nesting in the addon list, but every clause carries information.

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 two-parameter mutation with no output schema, the description covers the operation, the option semantics, eligibility caveats, and the return value (checkout_url) the caller must act on. Only the payment/completion follow-up flow is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 50% schema coverage, the description compensates for the undescribed 'addon' enum by giving a meaning per value, including eligibility caveats for 'office' and 'attorney'. The 'id' parameter is left to the schema, which documents it well, so the description does the work the schema cannot.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb ('Turn on') plus resource ('yearly add-on') scoped to 'a paid company', with each of the four addon values spelled out in plain language. An agent can distinguish this from remove_addon purely on the verb, and understand what is being enabled without opening the enum.

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?

Implicitly states the precondition that the company must be paid, and qualifies two values ('office, where available' and 'attorney, for a company registered in BC with its office elsewhere'). It gives no explicit when-not guidance and never names a sibling as an alternative, so the routing is inferred 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