Skip to main content
Glama

Base Token Audit — ERC-20 honeypot check and swap route data

Angel: 5,000 calls by card

buy_pack_with_card

For businesses without USDC: 5,000 calls €9.00, one-time, 90 days, businesses only, paid in EUR by card or Link. Returns checkout_url for a person to open; the checkout asks for the company or freelance name. After payment the success page (Accept: application/json) returns the key, and it is e-mailed. After: any tool with bundle_token.

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": "buy_pack_with_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
callsNo
emailNoWhere the key is sent (optional; Stripe asks otherwise).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / calls / default
      Previous value: -100New value: +5000
    • changedInput schema / properties / calls / enum
      Previous value: -[
      -  100,
      -  500,
      -  5000
      -]New value: +[
      +  5000
      +]
    • changedInput schema / properties / email / description
      Previous value: -"Where the token is sent (optional; Stripe asks otherwise)."New value: +"Where the key is sent (optional; Stripe asks otherwise)."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and openWorldHint=true; the description goes much further, disclosing that the call returns a checkout_url for a human to open, that checkout collects a company/freelance name, that the success page needs Accept: application/json to return the key, and that the key is also e-mailed. That out-of-band, human-in-the-loop payment flow is exactly the context an agent needs and cannot get from the annotations.

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?

Dense and front-loaded with price, quantity, duration, and eligibility before the flow details. A few phrases are terse to the point of ambiguity ('After: any tool with bundle_token', 'the checkout asks for the company or freelance name'), but no sentence 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 payment tool with no output schema and thin annotations, the description covers the return value, the human checkout step, the post-payment key retrieval, and the follow-up credential (bundle_token). It omits failure/abandonment behavior and whether checkout_url expires, which would matter for an agent deciding how long to wait or retry.

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 50%, with the email parameter documented and the calls parameter only an enum/default. The description compensates by fixing the meaning of calls (5,000 calls, €9.00, 90 days) and confirming the key is e-mailed, plus noting checkout fields not present in the schema (company/freelance name). It does not explain why email is optional or what Stripe does when it is omitted, so it is not fully compensating.

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 names a specific transaction: buying a 5,000-call bundle for €9.00, one-time, valid 90 days, paid in EUR by card or Link. It also scopes it to 'businesses without USDC', which implicitly distinguishes it from a crypto-payment path, and states the immediate output (checkout_url). An agent can tell exactly what this tool accomplishes without opening the schema.

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?

It gives a clear applicability condition ('for businesses without USDC', 'businesses only', EUR payment) and post-call sequencing ('After: any tool with bundle_token'). It stops short of naming a specific alternative purchase tool for the USDC case, so the routing guidance is implied rather than explicit.

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.