tmailor-mcp

Official

by tmailor-com

Overview Schema Source Related Servers Discussions Admin

Python

Remote

Account status and quota

account_status

Read-onlyIdempotent

Check remaining mailbox quota, active plans, and request rate for a Tmailor account to monitor usage limits and avoid interruptions.

Instructions

Show the remaining mailbox quota, the active plans and the request rate of the Tmailor account.

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

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`plans`	Yes
`addresses`	Yes
`client_ip`	Yes
`manage_url`	Yes
`quota_used`	Yes
`quota_total`	Yes
`quota_remaining`	Yes
`daily_request_cap`	Yes
`requests_per_minute`	Yes
`ip_allowlist_enforced`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 20, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so the safety profile is covered. The description adds only what data is surfaced (quota, plans, rate) and says nothing about auth requirements, rate limits, or freshness of the values, so it adds modest value beyond structured fields.

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?

A single front-loaded sentence that names the resource and the three data points with no filler. Nothing could be removed without losing information.

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 zero parameters, a complete annotation set, and an output schema documenting the return shape, the description only needs to convey scope — which it does. It stops short of noting any account-level access requirements, but nothing essential for invoking 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, which is the baseline-4 case. There are no parameter semantics for the description to clarify, and the schema fully covers the empty argument object.

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 specific verb ('Show') plus three concrete resources (remaining mailbox quota, active plans, request rate) scoped to the account. This is clearly distinguishable from every sibling, which operate on mailboxes, messages, or domains.

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 implied by the tool's scope: an agent wanting account-level quota/plan/rate info should call it. However, no explicit when-to-use guidance, prerequisites, or alternatives are given, and none of the siblings overlap enough to require routing advice.

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

Deploy Server