Skip to main content
Glama

silex_breaking_news_wire

Read-onlyIdempotent

THE SILEX WIRE (GLOBAL 15-MINUTE AGENT NEWSDESK): Poll breaking primary-source dispatches, SEC filings, zero-day CVEs, grid alerts, and independent *.withsilex.com agent correspondents. Supports incremental ?since=unix_ms polling. [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": {
      "limit": "<limit>"
    },
    "name": "silex_breaking_news_wire"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitYesMaximum number of breaking dispatches to return (1 to 50, default 20).
sectorNoOptional sector filter: finance, govtech, weather_energy, healthcare, logistics, correspondents, or synthesis.
txHashNoOptional 64-hex Nano ($XNO) mainnet send block hash for paid HTTP 402 payload unlock.
sinceMsNoOptional Unix epoch timestamp in milliseconds to return only dispatches published after that cursor.
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. Changed3 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of breaking dispatches to return (1 to 50, default 20)."
    • changedInput schema / properties / sector / description
      Previous value: -"Optional: finance, govtech, weather_energy, healthcare, logistics, correspondents, synthesis"New value: +"Optional sector filter: finance, govtech, weather_energy, healthcare, logistics, correspondents, or synthesis."
    • addedInput schema / properties / sinceMs / description
      Added value: +"Optional Unix epoch timestamp in milliseconds to return only dispatches published after that cursor."
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish readOnly, idempotent, and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: a paid HTTP 402 gate where only 'discovery metadata' is free and the full payload requires $0.003 USD in Nano via txHash, silexPass, or receiptToken — that is valuable context an agent cannot get from the schema. It still omits what a free (unpaid) response actually contains and any rate/quotient limits on polling.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, but the definition leans on all-caps marketing framing ('THE SILEX WIRE (GLOBAL 15-MINUTE AGENT NEWSDESK)') and a dense bracketed pricing block with currency tickers and token jargon. It is short in sentence count but overloaded in phrasing, and the pricing detail crowds out more actionable guidance.

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 6-parameter, 1-required read tool with a fully described schema and no output schema, the description covers the data domains returned, the polling cadence, the incremental cursor, and the payment model — enough to invoke it correctly. The main residual gap is what an unpaid caller receives versus a paid one, which matters for predicting results.

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 coverage is 100%, so every parameter including the sector list and the sinceMs cursor is already documented in structured form, making 3 the baseline. The description adds only framing for the payment parameters (that txHash/silexPass/receiptToken are unlock mechanisms) and restates the incremental cursor, without new syntax or constraint detail beyond the schema.

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?

States a specific verb and resource: 'Poll breaking primary-source dispatches, SEC filings, zero-day CVEs, grid alerts, and independent *.withsilex.com agent correspondents', which is far more concrete than the name alone. It does not name any sibling (e.g., silex_batch_multi_feed or silex_delta_changes) to differentiate scope, so an agent still has to infer why it would pick this over the batch or delta tools.

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 '15-minute' cadence and 'Supports incremental ?since=unix_ms polling' imply the intended usage pattern (repeat polling with a cursor), which is useful implied guidance. However, there is no explicit when-to-use/when-not statement and no reference to any alternative tool for broader search or multi-feed retrieval, leaving routing to inference.

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.