Piloxa – Certified Mail

Explain a Certified Mail status

explain_certified_mail_status

Read-onlyIdempotent

READ ONLY. Explains a USPS tracking status ("Notice Left", "Available for Pickup", "Unclaimed", "Refused", "Return to Sender", "Insufficient Address", "Delivered, Left with Individual"...) or a Piloxa transaction state (AWAITING_APPROVAL, VENDOR_ACCEPTED, MAILED, DELIVERED...) in plain words, with the likely next step and the guide that explains it. It explains the status in general; for a specific letter prepared in this conversation use get_certified_letter_status. It never says whether a notice is legally effective.

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": {
      "status": "<status>"
    },
    "name": "explain_certified_mail_status"
  }
}

Input Schema

Name	Required	Description	Default
`status`	Yes	The status text exactly as shown, e.g. "Notice Left (No Authorized Recipient Available)".

Output Schema

Name	Required	Description	Default
`id`	No
`kind`	No
`next`	Yes
`scope`	No
`status`	Yes
`meaning`	Yes
`guide_url`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already carry readOnlyHint and idempotentHint, so the 'READ ONLY' prefix is largely redundant, but the description adds real behavioral context: it returns the likely next step plus a linked guide, and it explicitly declines legal-effectiveness judgments. That limitation is valuable and unavailable from annotations.

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?

Front-loads the safety marker, then purpose, then sibling routing, then the scope limitation. The long status enumerations are purposeful but sit in the middle rather than delaying the key routing 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?

An output schema exists, so return-format explanation is unnecessary, and the description covers scope, ambiguity routing, and the legal-effect caveat. Minor gap: it doesn't say what happens with an unrecognized status string.

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?

Only one parameter, and the schema already documents it at 100% coverage including an example value. The description's status examples add flavor but no syntax beyond the schema, so the baseline 3 is appropriate.

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 (explains) plus the two distinct resource vocabularies it decodes (USPS tracking statuses and Piloxa transaction states) with concrete examples in quotes. An agent can immediately tell this apart from get_certified_letter_status.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use this one for a general status explanation, use get_certified_letter_status for a specific letter prepared in this conversation. That is a direct when/when-not with the alternative named.

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

All Piloxa – Certified Mail 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?