Skip to main content
Glama
Sign In
Market Intelligence MCP

Market Intelligence MCP

Official
by BullrunData
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

cascade_search

Read-only

Search for catalyst scenarios by keyword, matching against names, descriptions, categories, and trigger conditions to find relevant catalysts for a given situation.

Instructions

Search catalyst scenarios by keyword. Matches against catalyst names, descriptions, categories, and trigger conditions. Use this when you're not sure which catalyst applies to a given situation.

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": "cascade_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch query — e.g., "oil", "dollar", "china", "recession", "credit", "currency"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds context on what fields are searched (names, descriptions, categories, trigger conditions). No contradictions. It could mention response format, but that's not required given the tool's simplicity.

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?

Two sentences: the first clearly states the function, the second provides usage context. No unnecessary words. Information is front-loaded and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple search tool with one parameter, no output schema, and read-only annotations, the description covers all essential information: what it does, how it matches, and when to use it. It differentiates itself from sibling tools effectively.

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 coverage is 100% with a clear description of the 'query' parameter. The tool's description adds value by explaining what the query matches against (specific fields), which goes beyond the schema's generic description. This helps the agent understand the search scope.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states the verb 'Search' and the resource 'catalyst scenarios', and specifies that it matches against multiple fields (names, descriptions, categories, trigger conditions). It implicitly distinguishes from siblings like 'cascade_list' and 'cascade_by_category' by emphasizing free-text keyword search for uncertain situations.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description provides clear guidance: 'Use this when you're not sure which catalyst applies to a given situation.' This helps the agent choose between this tool and more specific siblings. It could improve by stating when not to use, but the existing guidance is sufficient.

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

Deploy Server

Other Tools