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).

concepts_news

Recent news mentioning the concept name (ILIKE on news.title + content). Short-term implementation; long-term will switch to AI tagging. Requires news:read scope.

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": {
      "concept_id": "<concept_id>"
    },
    "name": "concepts_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
daysNoLookback window in days (1-365, default 30)
limitNoMax items (1-200, default 50)
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
_max_bytesNo响应字节上限,默认约 50 KB
concept_idYesConcept primary key
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful traits: the required 'news:read' scope and the fact that matching is literal ILIKE substring matching, so synonym/entity-variant hits will be missed. It says nothing about result ordering (recency?), deduplication, or response shape, which are meaningful gaps for an unannotated tool.

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?

Three short sentences, front-loaded with the core purpose, then matching mechanics, then the auth requirement. The roadmap note ('long-term will switch to AI tagging') earns its place by flagging that recall behavior may change, though it is the most expendable clause.

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 filtered-list tool with no output schema and no annotations, the definition covers purpose, matching method, and the required scope — enough to call it correctly and to interpret why some mentions may be absent. Ordering and return shape remain unstated, but those are secondary for this tool's complexity.

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 baseline is 3; days, limit, and the generic _jq/_fields/_spill plumbing are all documented in the schema. The description adds the matching semantics behind concept_id (its name is matched against news text) but says nothing about the lookback window or cap parameters, which are the ones an agent most often needs to tune.

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+resource: recent news mentioning a given concept. The parenthetical '(ILIKE on news.title + content)' tells the agent exactly how matching is done, which is more than a name restatement. It does not explicitly distinguish itself from siblings such as news or news_get, so it stops 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?

Usage is implied by 'recent news mentioning the concept name' — an agent can infer this is the concept-scoped news lookup. However, there is no explicit when-to-use/when-not guidance and no named alternative (e.g., a general news feed or announcements_search) for other cases.

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