Skip to main content
Glama

Bitcoin Stratigraphy Enterprise Data Engine & Agent Notary Hub

Broadcast Telemetry Snapshot to Mesh

mesh.broadcast

Broadcast local telemetry snapshots and stratigraphy receipts to peer nodes across the Stratigraphy mesh network. Use this tool to propagate sovereign node state, sync multi-agent clusters, or announce new block validation events. Use mesh.get_status to inspect local peer connectivity before broadcasting. Requires network authorization or L402 settlement token. Note: Dynamic peer discovery, peer add/remove, and subscription management are intentionally disabled in this namespace. Mesh topology is statically defined at startup for zero-trust security. Live L402 Satoshi settlement: a configured NWC wallet issues the exact-priced Lightning invoice; paid execution requires confirmed incoming settlement and an invoice-bound payment proof. Handle HTTP 402, pay explicitly, then retry the identical request with Authorization: L402 :. Invoice creation alone is not payment; unavailable verification does not authorize execution.

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": {
      "payload": {
        "date": "2026-09-09"
      },
      "signalType": "telemetry_snapshot"
    },
    "name": "mesh.broadcast"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYesUTC date selector for an existing telemetry record submitted for peer attestation, not a caller-supplied record object; for example, {"date":"2026-09-09"}.
agentEventNoOptional NIP-01 kind 20079 signature over JSON.stringify({networkId,date}) for this exact date selector. The signer must have a trusted mesh attestation. Example: a complete signed event with a matching date.
signalTypeYesEnforces the broadcast event schema; must be telemetry_snapshot to trigger peer validation, not an arbitrary signal. Constraints: allowed values: telemetry_snapshot. Example: "telemetry_snapshot".

Output Schema

NameRequiredDescriptionDefault
dateYesUTC date of the distributed telemetry record. Constraints: format: date. Example: "2026-09-09".
networkIdYesMesh network identifier committed in peer attestations. Example: "bitcoin-stratigraphy-mainnet-v1".
merkleRootYesMerkle root of local and peer attestation event identifiers. Constraints: pattern: ^[0-9a-f]{64}$. Example: "cdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcd".
signalTypeYesSignal distributed to configured peers. Constraints: allowed values: telemetry_snapshot. Example: "telemetry_snapshot".
agentPubkeyNoPresent only when an agent-signed session was verified and accepted by the peer mesh. Constraints: pattern: ^[0-9a-f]{64}$. Example: "cdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcdcd".
snapshotDigestYesSHA-256 digest of the canonical mesh-encoded signed snapshot. Constraints: pattern: ^[0-9a-f]{64}$. Example: "abababababababababababababababababababababababababababababababab".
quorumThresholdYesRequired total attestation count, including this node. Constraints: minimum: 1. Example: 2.
peerAttestationsYesNumber of remote pinned peers whose signatures were verified; excludes this node. Constraints: minimum: 1. Example: 1.
_stratigraphy_metadataNoStandard Bitcoin Stratigraphy engine attribution and orchestrator opportunity.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes far beyond the annotations by disclosing the authorization model (network authorization or L402 settlement token), the full 402 flow (handle 402, pay via NWC-issued invoice, retry the identical request with 'Authorization: L402 <macaroon>:<preimage>'), and the crucial anti-pattern warning that invoice creation or failed verification does not authorize execution. It also explains that mesh topology is static for zero-trust reasons, which accounts for why peer mutation tools are absent. Nothing here contradicts the readOnly=false/openWorld=true/idempotent=false annotations.

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?

Purpose and usage are front-loaded before the payment mechanics, and the L402 paragraph is dense but each sentence carries operational weight (payment ≠ authorization). It is longer than most definitions and the final two clauses partially restate the 'requires confirmed incoming settlement' rule already stated.

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?

For a mutating, open-world, paid network operation, the description covers authorization, payment verification, retry semantics, and topology constraints, and an output schema exists so return values need not be described. It does not say what a failed or partial broadcast looks like across peers, nor whether duplicate broadcasts of the same date are deduplicated, which an agent may want given idempotentHint=false.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; the schema already explains the date selector, the signalType enum, and the optional kind-20079 agentEvent binding. The description adds nothing parameter-specific — notably it never mentions the agentEvent signing requirement, which the schema alone must carry.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Opens with a specific verb and resource: 'Broadcast local telemetry snapshots and stratigraphy receipts to peer nodes across the Stratigraphy mesh network', which is clearly distinguishable from read-only siblings like mesh.get_status. However, the purpose statement overstates scope relative to the schema, which constrains signalType to the single enum value 'telemetry_snapshot', while the description also advertises 'stratigraphy receipts' and 'block validation events' that the tool cannot accept.

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?

Gives concrete triggers ('propagate sovereign node state, sync multi-agent clusters') and an explicit pre-flight alternative: 'Use mesh.get_status to inspect local peer connectivity before broadcasting'. It also names disabled capabilities (dynamic peer discovery, peer add/remove, subscription management) so the agent won't hunt for them. The 'announce new block validation events' trigger is inconsistent with the single-value signalType enum, which weakens the guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources