Skip to main content
Glama
Sign In

GoodSender

by io.github.good-sender
OverviewDiscussionsAdmin

Check Sender Domain Stats

check_sender_domain_stats
Read-onlyIdempotent

Report each email sender domain's verification status, consent counts and email counts.

Verification status is refreshed from GoodSender on every call. Consent and email counts are the server's last known state (see ConsentStateAsOf); this tool never sends email. The result is a per-domain table: one row per sender domain, stats in columns.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
ConsentStateAsOfNoWhen consent counts and the queue were last refreshed from GoodSender; absent when not yet refreshed in this server session. This tool does not refresh them.
StatsPerSenderDomainYesStats per sender domain. Key is the domain, value is the domain stats.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes further with non-obvious traits: verification status is refreshed from GoodSender on every call while counts reflect the server's last known state, referenced via ConsentStateAsOf. That freshness/staleness distinction and the explicit 'never sends email' guarantee materially change how an agent should interpret the output.

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?

Three short sentences, front-loaded with what is reported, then data-freshness caveats, then the result shape. No filler; every sentence carries operational meaning.

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?

Although an output schema exists, the description still usefully orients the agent to a per-domain table with one row per sender domain. Combined with the freshness caveat and the no-side-effect guarantee, an agent has everything needed to call and interpret it correctly.

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; the empty schema is self-explanatory. Baseline 4 applies.

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?

States a specific verb and resource: 'Report each email sender domain's verification status, consent counts and email counts.' An agent immediately knows this is a per-domain read report. It does not explicitly distinguish itself from nearby siblings like list_sender_identities or list_recipients, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description establishes the usage context: aggregate stats per sender domain, and explicitly notes 'this tool never sends email,' which steers an agent away from the send_*/enqueue_* siblings. It does not name an explicit alternative or state when not to use it, so 4 rather than 5.

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

All GoodSender toolsInspect
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.

Resources