Skip to main content
Glama
benswel

QR for Agent

by benswel
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

upgrade_to_pro

Upgrade to the Pro plan for unlimited QR codes, scans, and webhooks. Returns a Stripe Checkout URL to complete payment and activate enhanced features.

Instructions

Upgrade to the Pro plan ($19/month) for unlimited QR codes, scans, and webhooks. Returns a Stripe Checkout URL — tell the user to open it in their browser to complete payment. The upgrade takes effect automatically after payment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • packages/mcp/src/tools.ts:723-730 (handler)
    The handler for `upgrade_to_pro` triggers a POST request to `/api/stripe/checkout` to initiate the Stripe checkout process for plan upgrades.
    upgrade_to_pro: {
  description:
    "Upgrade to the Pro plan ($19/month) for unlimited QR codes, scans, and webhooks. Returns a Stripe Checkout URL — tell the user to open it in their browser to complete payment. The upgrade takes effect automatically after payment.",
  inputSchema: z.object({}),
  handler: async () => {
    return apiRequest("/api/stripe/checkout", { method: "POST" });
  },
},

Tool Definition Quality

A4.2/5.0
Behavior4/5

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

With no annotations provided, description carries full burden and discloses key behavioral traits: returns external Stripe Checkout URL, requires browser-based completion, and automatic activation post-payment. Missing edge case handling (e.g., already Pro, duplicate calls).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tightly constructed sentences: benefit/value proposition first, return value and immediate action second, post-condition third. Zero redundancy; every sentence carries essential operational 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?

Given no output schema exists, description adequately compensates by specifying the Stripe Checkout URL return type and user instructions. Complete for the tool's complexity, though could mention error states or existing subscriber checks.

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?

Input schema has zero parameters, triggering baseline score of 4. Description correctly implies no user input is needed for the checkout URL generation.

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?

Excellent specificity: states exact action ('Upgrade to the Pro plan'), pricing ('$19/month'), specific benefits ('unlimited QR codes, scans, and webhooks'), and distinguishes clearly from sibling tools like 'manage_billing' and QR creation tools.

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?

Provides implied usage context (when user wants Pro upgrade) and explains the user workflow, but lacks explicit comparison to sibling 'manage_billing' which also handles billing-related operations. No 'when-not-to-use' guidance provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/benswel/qr-agent-core'

If you have feedback or need assistance with the MCP directory API, please join our Discord server