Skip to main content
Glama

silex_hyper_search

Search a permanent HTTP 402 data encyclopedia by keyword, CVE, ticker, ICAO, or operators. Return matched key:value proofs and discounted bulk topicPack URLs.

Instructions

Search With Silex permanent HTTP 402 data encyclopedia by keyword, phrase, CVE, ticker, ICAO, or operators (key:, domain:, sector:, max:, -exclude). Returns matched key:value proofs and 25%-off bulk topicPack URLs.

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
limitNo
queryYesSearch query, e.g. Microsoft, CVE-2026, XNO, KBOS, or key:cve_id
handleNoOptional subdomain filter, e.g. sec-filings or ciso-intel
sectorNoOptional sector filter, e.g. finance, govtech, grid, biomed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that results include matched key:value proofs and 25%-off bulk topicPack URLs, but does not clarify whether search itself requires payment/unlock, authentication, rate limits, or pagination; 'HTTP 402' hints at payment without explaining it.

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 dense sentences front-load the search action, then list query forms/operators and return content. Minor jargon ('topicPack', 'HTTP 402 data encyclopedia') and lack of segmentation reduce clarity slightly, but there is little wasted wording.

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?

For a four-parameter search tool with no output schema, it explains the query grammar and partially describes return content, which is helpful. However, with no annotations it leaves payment/unlock behavior and pagination unclear, which is material given the related payment and unlock tools.

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

Parameters4/5

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

Schema description coverage is 75%, so the baseline is 3, but the description adds useful search-operator syntax such as key:, domain:, sector:, max:, and -exclude beyond the schema examples. It does not explicitly map max: to the limit parameter, but it still adds meaningful query semantics.

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') and resource ('permanent HTTP 402 data encyclopedia'), plus accepted query forms such as keyword, CVE, ticker, ICAO, and operators. It does not explicitly distinguish itself from siblings like silex_live_pulse or silex_suggest_entities, so it falls short of a 5.

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?

Describes query forms and operators, implying this is the search entry point, but gives no explicit when-to-use versus when-not guidance or named alternatives. An agent must infer how this differs from live pulse, entity suggestion, or unlock-related siblings.

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