Bitcoin Stratigraphy Enterprise Data Engine & Agent Notary Hub

by app.replit.bitcoin-stratigraphy-dashboard--charlesstrogish

Read Authenticated Yield Staking Escrow

payment.get_escrow

Read-onlyIdempotent

PURPOSE & BOUNDARIES: Read the requesting NIP-98 signer's private staked yield in whole sats. Do NOT use this to withdraw or transfer funds, discover tool prices, or verify settlement; use payment.get_info for pricing and payment checks. USAGE GUIDELINES: Send empty arguments with fresh Nostr HTTP authentication bound to the exact URL, method and request body. No pubkey argument is accepted. BEHAVIOR & CONSEQUENCES: Free and read-only; missing or invalid authentication fails before lookup, and unavailable storage fails explicitly. vip_status is true strictly above 10000 sats. zero_latency_routing is an informational feature label, not a payment bypass or latency guarantee.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "payment.get_escrow"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`pubkey`	Yes	The fresh NIP-98 signer's public key.
`vip_status`	Yes	True strictly above 10000 whole staked sats.
`staked_sats`	Yes	Accumulated staked yield floored to whole satoshis.
`unlocked_features`	Yes	Informational feature identifiers; never a payment bypass or latency guarantee.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, yet the description still adds real value: it is free, auth failures occur before lookup, storage failures are explicit, and the vip_status threshold is stated as strictly above 10000 sats. The clarification that zero_latency_routing is merely an informational label (not a bypass or latency guarantee) preempts a plausible misinterpretation, though the return-shape discussion overlaps the existing output schema.

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?

Labeled sections (purpose/boundaries, usage, behavior) front-load the routing decision and exclusion before operational detail. Slightly dense with output-field commentary that the output schema already covers.

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?

For a zero-argument read tool with full annotations and an output schema, the description covers the only genuinely missing pieces: authentication requirements, failure ordering, and the semantic threshold behind vip_status.

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?

Zero parameters puts the baseline at 4, and the description reinforces it by stating no pubkey argument is accepted and that ownership is derived solely from request-bound authentication, which prevents an agent from inventing an identity parameter.

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 and resource — read the requesting signer's private staked yield in whole sats — and immediately carves out what it is not (withdraw/transfer, pricing, settlement verification) while naming the sibling payment.get_info for those cases.

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 instructs sending empty arguments with fresh Nostr HTTP auth bound to the exact URL, method and body, and names the alternative tool plus the conditions that select it, so the agent can route without inference.

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

All Bitcoin Stratigraphy Enterprise Data Engine & Agent Notary Hub 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?