Skip to main content
Glama

Where a human goes to change this site's plan

billing_link
Read-only

Use this when the customer has decided to upgrade, downgrade or cancel and needs the place to do it: 'how do I upgrade', 'where do I change my plan', 'send me the link', 'how do I cancel'. Use plan_options first if they are still deciding — that one has the prices and what each plan includes; this one is just the door. Returns the correct URL for this website's billing owner, which is not the same for every customer: a Shopify-billed store can only change plan on the Inclusify app's plan page in its own Shopify admin, a Wix-billed site only in its own Wix account (and that link has to be opened in a new tab), an Inclusify-billed website changes it on the website's page in the panel, and an invoice-managed website has no self-serve route at all — for that one this returns no link and says who to contact, rather than sending them somewhere that will not work. IMPORTANT: this returns a URL and does nothing else. It does not create a checkout session, does not charge a card, does not change a plan, and does not start a trial. Nothing on this server can — completing a plan change requires a human, signed in, in their own browser, and that is deliberate rather than a gap. Say so when handing the link over; do not imply the upgrade has been arranged. Works on every plan including Free. Read-only: one indexed read, no page load.

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": {
      "website": "<website>"
    },
    "name": "billing_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNoOptional. The plan the customer wants, so the link opens on that plan instead of the plan list. Omit it if they have not chosen one — the list page is the better landing.
websiteYesThe website domain as registered in Inclusify, e.g. "example.com".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false. The description still goes well beyond them: it discloses per-billing-provider routing (Shopify admin, Wix account with new-tab requirement, Inclusify panel, invoice-managed with no self-serve link), states the no-link fallback, and repeatedly warns it does not create a checkout session, charge a card, change a plan, or start a trial.

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?

Front-loaded with the when-to-use condition and the trigger phrases before the routing detail, which is the right order. It is on the long side, with several sentences re-emphasising what the tool does not do, though that repetition targets a real misuse risk rather than padding.

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?

The description covers the return value well enough (a URL, or no link plus a contact pointer for invoice-managed sites), which matters since there is no output schema. The routing matrix for the four billing owners is unusually complete for a 2-parameter tool, so no material gap remains.

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%, so the schema already documents both parameters, including the enum and the 'omit it if they have not chosen one' guidance. The description adds no meaning about the parameters, so the baseline 3 applies.

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?

States a specific verb and resource ('Returns the correct URL for this website's billing owner') and immediately distinguishes itself from the sibling 'plan_options' — 'this one is just the door.' An agent can tell the routing helper apart from the pricing helper without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit trigger utterances ('how do I upgrade', 'send me the link', 'how do I cancel'), names the alternative and the condition that selects it ('Use plan_options first if they are still deciding'), and states the exclusion clearly. Nothing about when to call this versus the sibling is left to inference.

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.