Skip to main content
Glama
This connector has been deprecated

Replaced by echopai-mcp.

Duplicate listing; superseded by io.github.echopai/echopai-mcp (official MCP Registry entry).

search

Structured-first hybrid search across analyst views + news (views weighted higher). Three lanes — entity (company codes / names, analyst names), concept-graph hub (theme alias → concept → constituents & research), and full-text keyword matching (Chinese word-segmented) — fused with RRF. Deterministic & explainable: no vector kNN, no LLM rerank. Best for theme/concept queries: 'CPO' brings out 光模块/光通信/光芯片; '减肥药' brings out 创新药; '智驾' brings out 智能驾驶. Use news or views instead if you need strict time-window listing.

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": {
      "q": "<q>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesFree-text query (Chinese or English)
_jqNoJMESPath,对 data 求值(写 items[*].id)
modeNohybrid = entity + concept-graph + full-text fused; exact = keyword full-text onlyhybrid
typeNoSearch scope (views weighted higher in 'all')all
hoursNoLookback window in hours; omit for no time limit
limitNoMax items returned
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
_max_bytesNo响应字节上限,默认约 50 KB
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose meaningful behavior: deterministic RRF fusion, no vector kNN, no LLM rerank, and views weighted higher than news in 'all'. What it omits is the response shape and how truncation/spill interact with the fused ranking — relevant because there is no output schema.

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?

Front-loaded with scope and mechanism, then guidance, then the routing hint — a sensible order. The concept-expansion examples are load-bearing rather than filler, though the lane enumeration makes it denser than strictly necessary for a search tool.

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 an 11-parameter tool with no output schema, the description covers query semantics well but says nothing about what a result item looks like, how views/news are interleaved in the fused ranking, or when a caller should reach for `_spill`. Enough to call correctly, not enough to interpret results confidently.

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 coverage is 100%, so the schema already documents `q`, `mode`, `type`, `hours`, `limit` and the underscore-prefixed utility params, making 3 the baseline. The description adds conceptual meaning for the lanes that `mode: hybrid|exact` switches between, but it does not explain `_jq`, `_spill`, `_fields`, or `_max_bytes` beyond what the schema already says.

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?

Names a specific verb and resource ('Structured-first hybrid search across analyst views + news') and then decomposes the mechanism into three named lanes (entity, concept-graph hub, full-text) fused with RRF. An agent can distinguish this from `news` and `views` without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit use case ('Best for theme/concept queries') reinforced with concrete query→expansion examples ('CPO' → 光模块/光通信, '减肥药' → 创新药), plus a named alternative and its selecting condition ('Use `news` or `views` instead if you need strict time-window listing'). When-to-use and when-not-to-use are both present.

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.

Resources