Skip to main content
Glama

Buy credits

buy_credits
Read-onlyIdempotent

Credit packs (100 = US$29, 500 = US$119, 2,000 = US$399, 10,000 = US$1,490) with their Stripe payment link. The link carries the client number, so credits load on their own once the payment completes. Give the link to the person as is; Fyrmo never asks for card details here.

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_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered; the description adds real behavioral context beyond them: the link embeds the client number, credits self-provision after payment, and card details are never collected here. This is exactly the kind of post-call consequence an agent needs. It does not state whether repeated calls return the same link (idempotency is only in 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?

Three tight sentences with the price table front-loaded and the handling instruction after, so the agent can act on the first read. The price enumeration is dense but earns its place by defining the returned resource; nothing is filler.

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 zero-parameter, no-output-schema tool this is largely sufficient: it explains the artifact, its pricing, and its payment lifecycle. The only omission is an explicit statement of the return shape (single link vs. set of links), which matters because no output schema exists to fill that gap.

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?

The tool takes zero parameters, so the baseline is 4 and no schema explanation is required. The pricing list adds useful meaning about what the tool returns, but it leaves a genuine ambiguity: with no pack-selection parameter, it is unclear whether the tool returns all four links or one, which the description never resolves.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete resource and outcome: credit packs at four price points, each paired with a Stripe payment link, with credits loading automatically after payment. It is clear what the agent gets back, though the verb is implied ('with their Stripe payment link') rather than stated, and no sibling is named as a contrast.

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?

It gives a clear operating instruction ('Give the link to the person as is') and implicitly scopes usage to credit purchase flows. It never says when not to use it, nor does it point to any alternative tool for pricing questions, contact reveals, or account lookups.

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