tollbooth-authority

authority_register_operator

Provision an operator in the Authority ledger.

Creates a ledger entry so the operator can purchase credits and certify purchase orders. Idempotent — safe to call again.

Requires TWO independent identity proofs:

proof — Schnorr proof signed by the candidate operator's npub. Proves the requester really controls that npub. The operator typically calls request_npub_proof / receive_npub_proof against this Authority first to mint a cached dpop_token.
authority_proof — Schnorr proof signed by the Authority's own npub. This is the Authority's human consent — only an agent with the Authority's nsec on hand can produce it. Apps generate this inline when the human admin clicks 'adopt'; otherwise an Authority-side proof can be minted the same way an operator-side one is.

Next step: Call purchase_credits to fund your credit balance.

Input Schema

TableJSON Schema

Name	Required	Description
`npub`	No	Your Nostr npub (bech32). Get one from the dpyc-oracle's how_to_join() tool.
`dpop_token`	No
`service_url`	No	Your MCP endpoint URL (e.g. 'https://my-service.fastmcp.app/mcp').
`display_name`	No	Human-readable name for the Operator service, shown in the community roster (e.g. 'my-service'). If empty, the roster falls back to a truncated npub.
`authority_proof`	No	Identity proof signed by the Authority's OWN npub — the Authority's discretionary consent to adopt this Operator. Apps with the Authority's nsec in their keystore (e.g. the Pricing Studio) produce this proof automatically when the user clicks 'adopt'.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 19, 2026

addedInput schema / properties / display_name

Added value: +{
+  "default": "",
+  "description": "Human-readable name for the Operator service, shown in the community roster (e.g. 'my-service'). If empty, the roster falls back to a truncated npub.",
+  "type": "string"
+}

First observedJul 16, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, description details effects: creates ledger entry, idempotent, requires two proofs. Lacks explicit side effects but covers key traits.

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?

Well-structured, front-loaded purpose, bullet-style proofs, efficient sentences. Every sentence adds value without redundancy.

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?

Covers purpose, prerequisites (two proofs), idempotency, next steps, and parameter origins. Complete for an agent given complexity and output schema exists.

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 covers 80% of parameters. Description adds value for dpop_token (origin from other tools) and explains proofs beyond schema. Adds workflow context.

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 it provisions an operator in the Authority ledger, enabling credit purchases and order certification. It distinguishes from siblings like deregister and adoption tools.

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?

Provides when to use: after operator proofs. Explains idempotency and next step (purchase_credits). Could explicitly state when not to use, but context is clear.

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

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