Skip to main content
Glama

upgrade_to_pro

Give the signed-in user a link to upgrade to Klyf Pro. Call this whenever the user asks to upgrade, subscribe, go Pro, pay, unlock Pro or paid features, remove limits, or asks how to get auto-reply or other Pro-only capabilities. Pass interval 'year' when the user asks for the annual, yearly, or discounted plan; otherwise leave it monthly.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "upgrade_to_pro"
  }
}

Input Schema

NameRequiredDescriptionDefault
intervalNoBilling interval: 'year' for the discounted annual plan, 'month' (default) for monthly

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false; the description adds the important nuance that the tool only produces a link rather than performing a charge, which tells the agent no payment happens server-side. It doesn't mention idempotency, whether a checkout session is created, or what the link looks like, which keeps it below 5.

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 core action in the first sentence, then usage triggers, then parameter rule — a sensible ordering. The trigger list is somewhat long but each phrase adds real routing vocabulary, so little is wasted.

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 single optional enum parameter with no output schema, the description covers the action, the return (a link), and the selection rule for the only parameter. Minor omissions are post-upgrade state handling and any auth/prerequisite note.

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?

Schema coverage is 100%, so the enum and default are already documented and the baseline is 3. The description adds decision value by mapping user phrasing ('annual, yearly, or discounted plan') to the 'year' value and defaulting to monthly otherwise, which is more actionable than the schema's wording.

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 concrete verb and resource ('Give the signed-in user a link to upgrade to Klyf Pro'), so the agent knows exactly what the tool returns without opening the schema. It is unmistakably distinct from every sibling tool, none of which touch billing.

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?

Lists explicit trigger intents (upgrade, subscribe, go Pro, pay, unlock paid features, remove limits, ask about auto-reply) plus a clear rule for choosing the interval, which is unusually strong routing guidance. The only gap is the absence of exclusions, e.g. what to do if the user is already Pro or asks about pricing without wanting a link.

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