Deeplead

Where the test email landed at each seed mailbox

deliverability_get_test

Read-only

Where the test email landed at each seed mailbox. Poll about once a minute while status is waiting. placement is inbox, spam, promotions, social, updates or forums, missing while the email has not arrived, or unreadable while we could not read that seed mailbox; score is the inbox share from 0 to 10 once the test is completed, leaving unreadable seeds out. rspamd is the content filter verdict with its matched rules, when a seed reports one.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "testId": "<testId>"
    },
    "name": "deliverability_get_test"
  }
}

Input Schema

Name	Required	Description	Default
`testId`	Yes	testId returned by deliverability_create_test

Output Schema

Name	Required	Description	Default
`score`	Yes
`seeds`	Yes
`rspamd`	Yes
`status`	Yes
`testId`	Yes
`closesAt`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 2, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds real behavioral context: the async waiting state, the full set of placement values including the sentinel values missing and unreadable, and how score is derived (inbox share 0–10, unreadable seeds excluded). It does not discuss error conditions or result expiry, so not a 5.

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?

It is front-loaded with the purpose and then packs field semantics into dense semicolon-linked clauses; every clause carries information. The run-on structure slightly hurts scannability but nothing is redundant.

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 read-only result-fetching tool with a rich output schema, the description covers what the agent needs: the polling cadence, the meaning of every placement value, and the scoring rule. Return shape is left to the output schema as expected.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single testId parameter already documents its pattern and its origin from deliverability_create_test. The description adds nothing about the parameter, so the baseline 3 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?

The description clearly states the resource returned: the placement result of a test email across each seed mailbox, which pairs naturally with the sibling deliverability_create_test. The retrieval verb is implicit rather than stated, but an agent can still distinguish this from the create tool without opening the schema.

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?

It gives an explicit operating instruction: poll roughly once per minute while status is waiting, which tells the agent both the condition to call and the cadence. It does not name an alternative tool or state when not to call, so it falls short of a full 5.

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

All Deeplead tools Inspect

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

Need Help?