tollbooth-authority-newengland

authority_receive_neon_402_alert

Inbound: an operator reports its Neon store is 402-locked.

Called MCP-to-MCP by the operator's runtime the instant it catches a Neon HTTP 402 on its own database. Verifies the operator controls npub (inline Schnorr bound to this tool's wire name), records a durable latest-state row, and fires a best-effort owner-notification DM. This is how the Authority learns the store is dark BEFORE a patron files a complaint.

Input Schema

TableJSON Schema

Name	Required	Description
`npub`	No	The reporting operator's Nostr npub (the one whose store is locked).
`detail`	No	Short, credential-free error summary (the Neon 402 message).
`dpop_token`	No	Inline kind-27235 proof signed by the operator's nsec, bound to this tool's wire name. The operator's runtime mints and sends this automatically when it catches a Neon 402.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 25, 2026

changedInput schema / properties / npub / description

Previous value: -"The reporting operator's Nostr npub (the one whose books are locked)."New value: +"The reporting operator's Nostr npub (the one whose store is locked)."

AddedJul 19, 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 bears the burden of behavioral disclosure. It details verification of npub via inline Schnorr bound to wire name, durable recording of state, and best-effort owner notification. It transparently mentions the 'best-effort' nature of the notification.

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 concise with two short paragraphs, front-loading the core purpose. Every sentence provides essential information without redundancy or fluff.

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?

Given the tool has an output schema and the description covers the full flow, from trigger to side effects, it is contextually complete. It explains the MCP-to-MCP invocation context and the strategic value (learning before complaint).

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 input schema has 100% coverage, providing descriptions for all three parameters. The description adds meaning to the dpop_token parameter, explaining it is an inline kind-27235 proof signed by the operator's nsec and automatically minted, which goes beyond the schema description.

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 what the tool does: it receives an operator's report of a Neon 402-locked store, verifies the operator's control over npub, records a latest-state row, and notifies the owner. It uniquely distinguishes itself among siblings by its specific inbound alert role.

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 explains the trigger condition (operator's runtime catches a Neon HTTP 402 and calls this tool MCP-to-MCP) and the purpose (Authority learns before complaint). However, it does not explicitly state when to avoid using this tool or list alternatives, though no direct alternatives exist among siblings.

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

All tollbooth-authority-newengland 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.