Skip to main content
Glama
Purelymail MCP

Purelymail MCP

by amplia-labs

Check account credit

check_account_credit
Read-only

Retrieve the current Purelymail account credit balance as a high-precision decimal string, so you can verify available funds before sending mail or planning usage.

Instructions

Returns the current account credit as a decimal string with up to 64 digits of precision.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral detail about the return type and precision, but it does not state currency or units, what account is checked, or any authentication or rate-limit context.

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?

The definition is a single sentence with no wasted words. The core action and resource are front-loaded, followed by the return format detail an agent would need.

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 read-only tool, the definition is nearly complete: annotations cover safety, and the description explains the return representation. The main remaining gap is that it does not clarify the currency or unit of the credit, which could matter when interpreting the decimal string.

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?

This tool has zero parameters, so the baseline is 4. The schema has no parameter descriptions to compensate for, and the description correctly focuses on the return value rather than inventing parameter semantics.

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 states a specific verb and resource: 'Returns the current account credit.' It also specifies the return representation, a decimal string with up to 64 digits of precision. This clearly distinguishes it from the sibling tools, which manage domains, users, passwords, and routing rules rather than account credit.

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 for checking account credit. There is no explicit when-to-use guidance, no exclusions, and no named alternatives. Because no sibling appears to expose account credit, the risk of choosing the wrong tool is low, but the description still provides no routing guidance.

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