Skip to main content
Glama

How to get a credential and add balance

how_to_buy
Read-onlyIdempotent

Read-only, free, no credential needed. Explains how to get a credential for the account tools of this server, how the prepaid balance is added, and where the Terms and the Acceptable Use Policy are. This server cannot create an account, take a payment or issue a credential.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally; the description adds the non-obvious facts that it is free, needs no credential, and cannot provision anything. It does not describe the shape of the explanatory response, but the tool is informational by nature so the practical risk is low.

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?

Two sentences, front-loaded with the callability facts ('Read-only, free, no credential needed') before the topic list and the capability limits. Every clause carries distinct information; nothing is redundant with the title.

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?

With no parameters, no output schema and full annotation coverage, the definition supplies enough for an agent to decide to call it and what topics the answer will address. A brief note on the form of the response (e.g., step-by-step instructions versus links) would close the remaining 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 schema-derived baseline of 4 applies; there is nothing for the description to disambiguate. Consistently, the description does not waste words on arguments that do not exist.

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 uses a specific verb ('Explains') plus the exact subjects covered: how to get a credential, how prepaid balance is added, and where the Terms and Acceptable Use Policy live. It also draws a hard boundary ('cannot create an account, take a payment or issue a credential'), which separates it from transactional siblings like buy_traffic_pack or rent_proxy.

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?

'Read-only, free, no credential needed' tells the agent it can be called unconditionally, including before onboarding. The negative scope statement implicitly routes account/payment/credential-issuance needs elsewhere, but no sibling is named explicitly as the alternative path.

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