Skip to main content
Glama

silex_delta_changes

Read-onlyIdempotent

Ultra-fast delta firehose returning ONLY subdomains and syntheses whose SHA-256 content mutated since your last epoch timestamp cursor. [Pricing: Free discovery metadata; full HTTP 402 payload unlock from $0.003 USD in Nano ($XNO) via txHash, silexPass, or receiptToken.]

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sinceMs": "<sinceMs>"
    },
    "name": "silex_delta_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
txHashNoOptional 64-hex Nano ($XNO) mainnet send block hash for paid HTTP 402 payload unlock.
sinceMsYesUnix epoch timestamp in milliseconds; returns only feeds whose SHA-256 content mutated after this time.
silexPassNoOptional Silex 0ms Prepaid Bearer Pass token (spass_...).
receiptTokenNoOptional 24h X-Silex-Receipt idempotent recovery token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / sinceMs / description
      Added value: +"Unix epoch timestamp in milliseconds; returns only feeds whose SHA-256 content mutated after this time."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior, so the description correctly spends its words on what annotations cannot convey: a per-call micropayment gate (HTTP 402), the distinction between free discovery metadata and paid full payload, and three separate unlock mechanisms. It does not explain what a caller receives when unpaid or what the delta records contain, so it is strong but not complete.

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?

Two sentences, front-loaded with the core behavior and followed by the pricing caveat in a bracketed aside. Nothing is repeated from the schema and no sentence is filler, though the jargon density ('delta firehose', 'syntheses') costs some readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of describing the response, and it only gestures at 'subdomains and syntheses' without saying what a mutated record looks like. The payment flow is mentioned but not sequenced (e.g., how txHash is obtained), leaving the paid path under-explained for a tool whose primary complication is billing.

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 all four parameters are already documented in the schema, including sinceMs semantics and the txHash pattern. The description reinforces the cursor meaning of sinceMs but adds no syntax, ordering, or precedence guidance for combining txHash, silexPass, and receiptToken, which is the one gap the schema leaves open.

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?

The description names a specific operation and scope: it returns 'ONLY subdomains and syntheses whose SHA-256 content mutated since your last epoch timestamp cursor,' which is a precise verb+resource+scope statement an agent can act on. It stops short of differentiating itself from siblings such as silex_breaking_news_wire or silex_hyper_search, so an agent must infer that this is the incremental-polling variant.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'since your last epoch timestamp cursor' implies this is for incremental polling after an initial full fetch, but the description never states when to prefer this over the full-content siblings or what to do on a first call with no cursor. No explicit when-not-to-use or alternative routing is provided.

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.