Skip to main content
Glama

silex_live_questions

Read-onlyIdempotent

Fetch 53 real-time natural-language Q&A briefings synthesized every 15 minutes across SEC, CISA KEV, NOAA, ERCOT, NIH, FDA, and crypto orderbooks.

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": {
      "keyword": "<keyword>"
    },
    "name": "silex_live_questions"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordYesKeyword or topic filter to match live 15-minute Q&A briefings (pass 'all' to return all 53 feeds).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / keyword / description
      Added value: +"Keyword or topic filter to match live 15-minute Q&A briefings (pass 'all' to return all 53 feeds)."
  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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's genuine addition is the freshness contract ('synthesized every 15 minutes') and the breadth of sources, but it says nothing about result size, latency, or how results shrink under a narrow keyword.

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?

One sentence with the verb, resource, cadence, and source coverage front-loaded and no filler. Every clause carries information an agent would otherwise have to guess.

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 single-required-parameter, read-only retrieval tool with no output schema, the description supplies the essential context: what is returned (NL Q&A briefings), how stale it can be (15 minutes), and how broad the corpus is. It stops short of describing the response shape or what a narrow keyword yields, which would matter given no output schema exists.

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%, and the schema itself explains the keyword filter and the 'all' escape hatch, so the baseline of 3 applies. The mention of specific domains (SEC, NOAA, ERCOT, etc.) implicitly hints at what keywords can target but adds no syntax or matching rules 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?

A concrete verb and resource ('Fetch ... Q&A briefings') plus an explicit scope of seven named source domains and the 53-feed count. It separates itself reasonably from ask-style siblings like silex_ask_instant by framing the operation as retrieval of pre-synthesized briefings, though it never explicitly names 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 Guidelines2/5

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

States no when-to-use or when-not-to-use conditions and points to no alternatives, even though siblings such as silex_ask_instant and silex_breaking_news_wire clearly overlap in the live-data space. The only guidance ('pass all') lives in the schema, not the description.

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.