CallForMe

Account balance

account

Read-onlyIdempotent

The user's CallForMe balance, auto-reload setting, recent spend and projected run-out date, the "pause calls under" setting, their most recent call, and a link to add credit. Use it when the user asks about their balance, spend or settings, or before a large call_around to check the balance covers it; for what calls cost, use pricing (no account needed). Having no account yet is normal until the first real call. Auto-reload and the pause setting are changed by the user on the account page (the link it returns), not 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": "account"
  }
}

Input Schema

Name	Required	Description	Default
`account_key`	No	Only for clients without OAuth: the cfm_ API key (from the account page or an earlier setup). Leave out when connected with OAuth.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful behavioral context beyond annotations: no account is normal until the first real call, and auto-reload/pause settings are changed on the returned account page rather than through this tool.

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 returned data and then moves into usage guidance and constraints. It is dense and somewhat run-on, but every clause carries useful information and there is no filler.

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?

There is no output schema, so the description carries the return-value burden and lists the account fields an agent would need. It also covers the no-account edge case and where settings must be changed, leaving little relevant context missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter is fully documented in the schema, including when to omit it for OAuth clients. The description does not add further parameter guidance, but with 100% schema coverage the baseline score is appropriate.

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 the exact account data returned: balance, auto-reload, recent spend, projected run-out date, pause setting, most recent call, and add-credit link. It also distinguishes this from the pricing tool, so an agent can tell what resource this retrieves versus siblings.

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?

It gives explicit triggers: when the user asks about balance, spend, or settings, and before a large call_around. It also names the alternative for call costs (pricing) and states that pricing needs no account, which directly guides tool selection.

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

All CallForMe tools Inspect

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.