Skip to main content
Glama

Inclusify Accessibility

by com.inclusifyapp
OverviewDiscussionsAdmin

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 Shopify's managed-pricing page in its own 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.

Input Schema

TableJSON 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.6/5.0
Behavior5/5

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

Annotations already provide readOnlyHint=true and destructiveHint=false, and the description goes well beyond them: it explains that the billing link differs by billing platform, that Wix links must open in a new tab, that invoice-managed customers get a contact instead of a dead link, and that the tool performs no side effects whatsoever (no checkout, no card charge, no plan change). This is rich behavioral context that prevents an agent from overpromising to the user.

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?

The description is dense but every sentence serves a purpose: routing, scope, per-platform behavior, and no-side-effects guarantee. It is longer than the ideal, but the length is justified by the complex billing-platform variance. Only minor redundancy (e.g., 'this one is just the door' after the routing) keeps it from a 5.

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

Completeness5/5

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

For a single-required-parameter tool with full schema coverage, read-only annotations, and no output schema, the description covers everything an agent needs: when to call, what it returns (URL or contact info, depending on billing type), what it does not do, and how to frame the result to the user. There is no material gap.

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% and the two parameters are fully described there. The description adds the purposeful distinction for the optional `plan` parameter (opens on a specific plan vs. the plan list), which is genuine added value, but the rest of the semantics are already encoded in the schema. Baseline 3 is appropriate.

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?

The description clearly identifies the specific action (obtaining a self-service billing link), the exact resource (billing page for the customer), and the key scope constraint (URL only, not a transaction). It also names the sibling `plan_options` to distinguish planning from purchasing, so an agent can disambiguate without opening schemas.

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?

Provides explicit when-to-use signals (customer has decided to upgrade/downgrade/cancel), an explicit alternative (`use plan_options first if they are still deciding`), and even describes the not-a-fit case (invoice-managed has no link, contact instead). This is the strongest form of usage guidance: when, when-not, and the sibling that covers the other case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Inclusify Accessibility toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources