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

news_get

Fetch one news item by id — the read half of list→read, for when a news list row is not enough. Returns that item's full content plus its tagged securities and source labels. ⚠️ Field author is the byline entity — an outlet brand or a social account handle, never a reporter's name (reporter bylines are split off at ingest), so do not present it as a person; source_label is the collector-level source. Remember news is the SUPPLEMENTARY stream: for forming an investment opinion prefer views. Free, and takes no scope of its own.

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": {
      "news_id": "<news_id>"
    },
    "name": "news_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
_spillNotrue=全量落盘,只回摘要与取数地址
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
news_idYesNews id from a `news` list row (items[].id)
_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?

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the returned fields, clarifies that `source_label` is collector-level, and gives a strong field-semantics warning that `author` is an outlet brand or social handle rather than a reporter. It does not cover failure behavior (e.g., unknown id) or rate/limit context beyond "free."

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 purpose and positioning in the first clause, then returns, then the caveat. The `author` warning is longer than the rest combined but is a genuine misuse guard rather than filler; the only mild redundancy is restating that `news` is supplementary after already deferring to `views`.

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 single-item read with no output schema and no annotations, the description covers purpose, return fields, and the key field-semantics trap. It leaves gaps on error behavior for a missing or invalid id and on how truncation or spilling interacts with the returned content, which matters given `_max_bytes` and `_spill` on the schema.

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 all seven parameters including `news_id`, `_jq`, `_fields`, and `_max_bytes` are already documented in the schema. The description only echoes the id's provenance ("from a `news` list row"), adding no format or edge-case semantics beyond what the schema provides.

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?

States a specific verb and resource ("Fetch one news item by id") and positions it explicitly as "the read half of list→read," which distinguishes it from the `news` list sibling. It also states what comes back (full content plus tagged securities and source labels), so the agent knows the shape of the result before opening the 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?

Names the trigger condition directly: use it "when a `news` list row is not enough," which implies the sibling `news` is the default for list-level scanning. It also routes the agent away from this tool for opinion-forming ("prefer `views`") and notes it is free and takes no scope, so there is no prerequisite to resolve first.

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