Skip to main content
Glama

Data Candy: US business leads

Account status

account_status
Read-onlyIdempotent

Show the account behind your API key: email, plan, credit balance, today's usage and spend limits. Needs an API key (Authorization: Bearer dc_live_... or X-API-Key).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
planNoThe monthly plan, or null when the account has only prepaid credits.
emailNo
linksYes
key_prefixNoThe first characters of the API key in use (never the whole key).
plan_usageNoLeads used today against the plan's daily allowance (plan customers only).
credits_usdNoPrepaid credit balance in dollars.
credits_centsNo
spent_today_usdNo
spend_limit_daily_usdNoThis key's daily spend limit, or null for none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and a closed world, so the safety profile is covered. The description adds genuinely non-structured context: it requires an API key and accepts either Authorization: Bearer dc_live_... or X-API-Key, which is exactly the auth prerequisite an agent needs before invoking.

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 what is returned, then the prerequisite. Every clause carries information an agent needs; there is no restating of the title or 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?

For a parameterless read tool with an output schema, the description covers the two things structured fields cannot: the exact fields returned and the credential requirement including header formats. Nothing an agent needs in order to call it correctly 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly avoids inventing inputs and instead spends its words on scope and auth.

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 concrete verb and resource ("Show the account behind your API key") and enumerates exactly what comes back: email, plan, credit balance, today's usage, spend limits. That distinguishes it from siblings like create_account or add_credits, which mutate rather than read account state.

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?

Usage is only implied: an agent can infer this is the tool to call to inspect account/credit state, but the description never says when to prefer it over siblings (e.g. before buy_leads or quote_leads to check balance) nor any when-not condition. No alternatives are named.

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