Skip to main content
Glama

silex_hyper_search

Read-onlyIdempotent

Hyper-specific keyword, exact phrase, CVE, ticker, ICAO, or key:field search across 435+ permanent paywalls. [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": {
      "query": "<query>"
    },
    "name": "silex_hyper_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoOptional maximum number of matching paywall records to return (default 20, max 50).
queryYesKeyword, exact quoted phrase, CVE ID, stock ticker, airport ICAO code, or key:value filter to search.
handleNoOptional single subdomain handle filter (e.g. sec-filings, ciso-intel, notam-flight).
sectorNoOptional sector filter (e.g. finance, govtech, grid, biomed, logistics, travel, ansi, college, game).
txHashNoOptional 64-hex Nano ($XNO) mainnet send block hash for paid HTTP 402 payload unlock.
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. Changed4 schema fields changed
    • addedInput schema / properties / handle / description
      Added value: +"Optional single subdomain handle filter (e.g. sec-filings, ciso-intel, notam-flight)."
    • addedInput schema / properties / limit / description
      Added value: +"Optional maximum number of matching paywall records to return (default 20, max 50)."
    • addedInput schema / properties / query / description
      Added value: +"Keyword, exact quoted phrase, CVE ID, stock ticker, airport ICAO code, or key:value filter to search."
    • addedInput schema / properties / sector / description
      Added value: +"Optional sector filter (e.g. finance, govtech, grid, biomed, logistics, travel, ansi, college, game)."
  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 declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful economics — free discovery metadata with a paid HTTP 402 payload unlock from $0.003 in Nano via txHash, silexPass, or receiptToken — which no annotation conveys. It stops short of saying what the free metadata contains versus the paid payload, or how results are paginated.

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, purpose front-loaded, no filler. The bracketed pricing block is dense but self-contained and clearly marked as secondary to the search description.

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?

With no output schema, seven parameters, and a paid-unlock flow, the description should clarify what the free discovery response returns versus what requires payment, and whether limit applies before or after unlock. It flags the monetization model but leaves that return-shape question open, which is the main gap for an agent deciding whether to spend.

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 seven parameters are already documented, and the description's query-type enumeration largely restates the schema's query description. The payment-token mention echoes the txHash/silexPass/receiptToken schema entries without adding precedence or fallback rules (e.g., which credential wins if several are supplied). Baseline 3 is appropriate.

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 (search) plus the resource (435+ permanent paywalls) and enumerates accepted query shapes: keyword, exact phrase, CVE, ticker, ICAO, key:field. That is far more specific than the name alone, though it never contrasts itself with siblings like silex_encyclopedia_lookup or silex_ask_instant, so an agent must infer the boundary.

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 list of query types implies when the tool fits (identifier lookups, exact phrases, faceted filters), but there is no explicit when-to-use, when-not, or named alternative among the fourteen sibling tools. The bracketed pricing sentence occupies space that could have carried routing 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.