tollbooth-sample

weather_receive_npub_proof

Receive npub ownership confirmation from a patron.

Completes the npub-OWNERSHIP-PROOF flow (the credential-delivery counterpart is receive_credentials).

Call this only after the user confirms they have replied. Deterministic, one-shot retrieval: name the response with (patron_npub, dpop_token) — the dpop_token being the value returned by request_npub_proof. The tool drains ONLY the pinned rendezvous relay that challenge was published on, stopping at the DM whose phrase matches. Mismatched DMs are deleted and NACK'd (without revealing the expected phrase). If called before the user replies, their message will never be found. Do NOT poll, loop, or retry.

The signed DM itself proves npub ownership (the patron's nsec signed it). On success, returns the dpop_token — the same token. The calling application MUST remember it and pass it as the dpop_token parameter on every subsequent paid tool call. The proof (a hash of the token) is stored in the vault keyed by that hash — the MCP never stores the raw token itself. Free.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`dpop_token`	No	Required. The dpop_token returned by request_npub_proof.
`patron_npub`	No	Required. The patron's npub to receive proof from.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 16, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With no annotations provided, the description fully discloses behavioral traits: it drains only the pinned rendezvous relay, stops at the first matching DM, deletes and NACKs mismatched DMs without revealing the expected phrase, and explains the token handling and storage. The non-deterministic outcome if called too early is also noted.

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?

The description is informative but somewhat lengthy. It includes necessary details without redundancy, and key instructions are front-loaded. However, it could be slightly more concise by removing minor clarifications that could be inferred from context.

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?

Given the complexity of the flow and the presence of an output schema (assumed adequate), the description covers the essential aspects: purpose, prerequisites, behavior, and return value. It explains the proof mechanism and token lifecycle sufficiently for an AI agent to use the tool 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?

Although the input schema covers both parameters and provides descriptions, the description adds value by clarifying the relational context: 'dpop_token' is the value returned by 'request_npub_proof' and must be remembered, and 'patron_npub' is the patron's npub. This contextual linkage enhances understanding beyond the schema alone.

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?

The description clearly states the tool receives npub ownership confirmation and completes the npub-OWNERSHIP-PROOF flow. It distinguishes itself from the sibling tool 'receive_credentials' by specifying it is the credential-delivery counterpart. The verb 'receive' and resource 'npub ownership proof' are specific and unambiguous.

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?

Explicit usage instructions are provided: 'Call this only after the user confirms they have replied.' It warns against polling, looping, or retrying, and explains the one-shot deterministic nature. The conditions for successful execution are clearly stated, including the requirement for the user's reply to be present.

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

All tollbooth-sample 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.