Skip to main content
Glama
Sign In

AutomateSocials

by net.automatesocials
OverviewDiscussionsAdmin

Buy credits

buy_credits

Returns a Stripe checkout link for a credit pack. Nothing is charged until the user opens the link and pays; the credits are added to their account as soon as Stripe confirms the payment. Packs: starter (50 credits, $4.99), growth (200, $14.99), power (500, $29.99), power_plus (1000, $49.99). Credits never expire. Give the user the link; never claim the credits were added.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "packageId": "<packageId>"
    },
    "name": "buy_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault
packageIdYesstarter, growth, power or power_plus.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say this is a non-read-only, open-world, non-destructive, non-idempotent call; the description adds the critical facts that nothing is charged at call time, credits are applied only after Stripe confirms payment, credits never expire, and the agent must not misrepresent success. That is exactly the behavioural context annotations cannot carry.

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?

Front-loaded with what the tool returns, then the payment semantics, then the pack table, then the operational instruction. No sentence is filler and the price list is compactly formatted.

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?

Covers return value (a checkout link), timing of side effects, pricing options, and the guard against false success claims. For a single-parameter non-idempotent purchase tool, nothing an agent needs is missing.

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% and the enum is already documented, but the description adds real value by mapping each package to its credit count and price (starter 50/$4.99 through power_plus 1000/$49.99). This lets the agent present meaningful options to the user.

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 specific verb and resource ('Returns a Stripe checkout link for a credit pack'), which clearly separates it from the read-only sibling get_credits. An agent can distinguish purchasing from balance-checking without opening either 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?

Implicitly scopes usage by describing the purchase flow and instructing 'Give the user the link; never claim the credits were added', which sets the correct post-call behaviour. It does not explicitly name get_credits as the alternative for checking balance, so routing guidance is contextual rather than explicit.

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

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