Skip to main content
Glama

silex_batch_multi_feed

Read-onlyIdempotent

Query or unlock up to 12 subdomains in ONE round-trip (30% batch discount) with optional column projection (fields) and compact/tsv encoding (65% fewer tokens). [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": {
      "handles": "<handles>"
    },
    "name": "silex_batch_multi_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoOptional comma-separated JSON field names for column projection to reduce token count.
formatNoOptional output encoding format: 'json' (default), 'compact', or 'tsv' for 65% lower token usage.
txHashNoOptional 64-hex Nano ($XNO) mainnet send block hash for paid HTTP 402 payload unlock.
handlesYesArray of 1 to 12 With Silex subdomain handles to query in one round-trip (e.g. ['oracle-alpha', 'ciso-intel']).
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. Changed6 schema fields changed
    • addedInput schema / properties / fields / description
      Added value: +"Optional comma-separated JSON field names for column projection to reduce token count."
    • addedInput schema / properties / format / description
      Added value: +"Optional output encoding format: 'json' (default), 'compact', or 'tsv' for 65% lower token usage."
    • addedInput schema / properties / handles / description
      Added value: +"Array of 1 to 12 With Silex subdomain handles to query in one round-trip (e.g. ['oracle-alpha', 'ciso-intel'])."
    • addedInput schema / properties / silexPass / description
      Added value: +"Optional Silex 0ms Prepaid Bearer Pass token (spass_...)."
    • addedInput schema / properties / txHash / description
      Added value: +"Optional 64-hex Nano ($XNO) mainnet send block hash for paid HTTP 402 payload unlock."
    • addedInput schema / properties / txHash / pattern
      Added value: +"^[0-9a-fA-F]{64}$"
  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 declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the 30% batch discount, the free-vs-paid payload split, and the three unlock credentials (txHash, silexPass, receiptToken). It does not describe what happens when some handles are free and others gated, or error behavior past the 12 limit.

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?

Two sentences, front-loaded with the capability and its quantitative payoff before the pricing bracket. The bracketed pricing sentence is dense and slightly noisy but does carry decision-relevant cost information, so it earns its place.

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 six-parameter batch query with a fully described schema, no output schema, and read-only annotations, the description covers scope limits, encoding trade-offs, and the payment path an agent must know about. The remaining gap is mixed free/paid handle behavior and failure modes, which are minor for a read-only query.

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 six parameters are already documented in structured form, establishing a baseline of 3. The description reinforces the rationale for 'fields' (column projection) and 'format' (compact/tsv token savings) and enumerates the payment credentials, but adds little syntax or constraint detail the schema does not already 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?

The description states a specific verb pair ('query or unlock') plus the resource ('up to 12 subdomains') and the defining trait of batching in one round-trip. It is clearly distinguishable from single-feed siblings like silex_ask_instant, though it never names an alternative to sharpen the contrast.

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?

Usage is implied by the batching constraint and the two pricing tiers (free discovery metadata vs. paid 402 payload unlock), which lets an agent reason about cost. However, there is no explicit when-not-to-use statement or named alternative for single-handle lookups, so selection guidance is only partially covered.

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.