taxsort-mcp

taxsort_receive_credentials

Pick up credentials from the Secure Courier.

Completes the CREDENTIAL-DELIVERY flow (the ownership-proof counterpart is receive_npub_proof).

Call this only after the user confirms they have replied. Deterministic, one-shot retrieval: name the response you want with (sender_npub, service, dpop_token) and the tool drains ONLY the rendezvous relay that channel was pinned to. Every popped DM with the wrong session phrase is deleted and its sender is NACK'd; the first DM with the matching phrase is accepted (ACK'd) and the scan stops. If none match, the queue is drained and a courier_not_found result is returned. Do NOT poll, loop, or retry.

If a credential_card (ncred1...) is provided, it is redeemed directly without any relay access (dpop_token not required for that path). On success, the payment processor client is reinitialized from the new credentials — no server restart needed.

Input Schema

TableJSON Schema

Name	Required	Description
`service`	No	Required. The credential service name (must match the service used in request_credential_channel).
`dpop_token`	No	Required. The session phrase returned by request_credential_channel for this exact channel.
`sender_npub`	No	Required. The npub that sent the credentials.
`credential_card`	No	Optional. An ncred1... card to redeem directly (bypasses the relay drain; dpop_token not needed).

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedAug 30, 2026

addedInput schema / properties / credential_card / description

Added value: +"Optional. An ncred1... card to redeem directly\n(bypasses the relay drain; dpop_token not needed)."

addedInput schema / properties / dpop_token / description

Added value: +"Required. The session phrase returned by\nrequest_credential_channel for this exact channel."

addedInput schema / properties / sender_npub / description

Added value: +"Required. The npub that sent the credentials."

addedInput schema / properties / service / description

Added value: +"Required. The credential service name (must match\nthe service used in request_credential_channel)."

First observedJul 16, 2026

TDQS

A4.9/5.0

Behavior5/5

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

With no annotations provided, the description fully carries the behavioral burden. It discloses deterministic one-shot retrieval, relay draining, deletion and NACK of wrong-phrase DMs, ACK-and-stop on the first match, courier_not_found on no match, and payment-processor reinitialization. This is exceptionally transparent.

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 description is dense but each sentence earns its place: intro, flow context, precondition, deterministic behavior, failure result, and the alternative credential_card path. The structure front-loads the core purpose and then layers crucial operational constraints.

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?

Despite lacking annotations, the description covers preconditions, side effects, failure modes, the no-poll rule, and the alternative redemption path. An output schema exists, so detailed return-value documentation is not required here. This is a thorough, self-contained definition.

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?

Schema coverage is 100% and each parameter already has a description. The tool description adds meaningful relational context by grouping (sender_npub, service, dpop_token) as the response identifier and explaining that credential_card bypasses relay access and makes dpop_token unnecessary, which the schema alone does not convey.

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?

Opens with a specific verb and resource ('Pick up credentials from the Secure Courier') and immediately connects to the CREDENTIAL-DELIVERY flow. It names the ownership-proof counterpart receive_npub_proof, so an agent can distinguish this tool from its sibling without ambiguity.

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 states the precondition ('Call this only after the user confirms they have replied'), warns against polling/looping/retrying, and names the alternative flow (receive_npub_proof). It also disambiguates the two invocation modes: relay drain vs credential_card redemption.

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

All taxsort-mcp 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.