Skip to main content
Glama

Safe-Send Check: crypto support triage, sanctions and scam screening

Credits left on your key (free)

credits_balance
Read-onlyIdempotent

FREE. Credits left and calls made on the key sent as the MCP header "Authorization: Bearer ssk_..." (or _meta["safe-send/credits-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": "credits_balance"
  }
}

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, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely non-structured context: which credential the call is scoped to and the two ways that credential can be supplied (Authorization header or _meta key), which an agent cannot derive from the empty schema. It stops short of describing the response payload or behavior on a missing/invalid key.

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?

Two compact sentences with the cost signal front-loaded. The main clause is compressed almost to the point of awkwardness ('Credits left and calls made on the key sent as the MCP header...') and reads more as a noun phrase than a statement of what the tool returns, costing a point.

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-param, read-only, no-output-schema tool, the definition covers the essentials: what it returns, that it is free, and how the key is resolved. Missing only edge behavior — no-key case and the shape of the returned balance — which is minor at this complexity.

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?

With zero parameters and 100% schema coverage, the baseline is 4. The description goes slightly beyond by explaining the implicit input source — the auth header or _meta['safe-send/credits-key'] — which the empty schema does not capture.

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 names a specific resource (credits remaining) plus a secondary metric (calls made) tied to a specific credential. It is clearly informational rather than a claim/quote flow like the credits_claim and credits_quote siblings, though it never names those siblings to sharpen the distinction.

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 its remaining balance, and the leading 'FREE' signals it costs no credits to invoke. There is no explicit statement of when to prefer this over credits_quote or credits_claim, and no note about what happens when no resolution of the key occurs.

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