Skip to main content
Glama

Attestwire

by com.attestwire
OverviewDiscussionsAdmin

Get a checkout link to upgrade a key

get_upgrade_link

Return a hosted checkout URL for upgrading an Attestwire key to a paid plan (Solo: 1,000 documents/month for €9/month; Starter: 5,000 for €29/month; Scale: 50,000 for €99/month (EUR, plus VAT where due)). THIS DOES NOT BUY ANYTHING. It creates a checkout link and charges nothing; a human must open the link, enter their own card and confirm the recurring charge in the Paddle checkout. You cannot complete the purchase and must not report it as completed. Call this ONLY when the user has asked to upgrade or has agreed to see a checkout link, and only with the plan they chose. On quota_exceeded, tell the user the limit is reached and that paid plans exist; do not call this until they say which plan they want. Monthly billing only here; annual plans are on https://attestwire.com/pricing. Costs no documents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoThe Attestwire API key to upgrade (aw_live_...). Optional if this server is configured with an Authorization header, which is read instead.
planYesWhich paid plan to price up: "solo" (€9/mo) or "starter" (€29/mo) or "scale" (€99/mo).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / plan / description
      Previous value: -"Which paid plan to price up: \"starter\" ($49/mo) or \"scale\" ($199/mo)."New value: +"Which paid plan to price up: \"solo\" (€9/mo) or \"starter\" (€29/mo) or \"scale\" (€99/mo)."
    • changedInput schema / properties / plan / enum
      Previous value: -[
-  "starter",
-  "scale"
-]New value: +[
+  "solo",
+  "starter",
+  "scale"
+]
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Despite annotations indicating non-read-only and non-idempotent, the description adds crucial behavioral context: it does NOT buy anything, charges nothing, requires human confirmation, and the agent cannot complete or report the purchase. It also states 'Costs no documents.' This goes well beyond the annotations and prevents misuse.

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 front-loaded with the core purpose and then provides essential caveats in a logical order. While somewhat long, every sentence carries necessary information—no fluff. The use of capitalization for emphasis is effective.

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 tool with no output schema, the description adequately explains the return value (hosted checkout URL), side effects (none), prerequisites (user consent), and limitations (cannot complete purchase). It leaves no critical gap for correct invocation.

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% with both parameters described, but the description enriches the 'plan' parameter by adding prices and document limits, and clarifies the optional nature of 'key' when an Authorization header is present. This adds value beyond the schema.

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 states a specific action (return a hosted checkout URL) and the resource (upgrading an Attestwire key to a paid plan). It lists plan names and prices, making the purpose unambiguous and distinct from any sibling tool.

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?

Explicit guidance: call ONLY when the user asks to upgrade or agrees to see a checkout link, and only with the chosen plan. Also provides a clear alternative (annual plans on the pricing page) and instructs when NOT to call (until the user specifies a plan on quota_exceeded).

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

All Attestwire 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