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

views_get

Fetch one analyst view by id — the read half of list→read, for when a views list row is not enough. Returns that view's complete body (never truncated, regardless of the fields mode the list was fetched with), its AI summary, attached images, and tagged securities. Use it on any id from views; that includes the ~90% of the feed that are plain analyst opinion rather than archived reports. ⚠️ This is not report. report returns the parsed long-form text of an archived sell-side PDF and only works where full_text_available=true; this returns the view record itself and works on every id. If the list row already carries what you need, do not call this — a views page at fields=full has the body inline. 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": {
      "view_id": "<view_id>"
    },
    "name": "views_get"
  }
}

Input Schema

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

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

With no annotations, the description carries the full burden and does real work: it discloses cost ('Free'), scope ('takes no scope of its own'), coverage ('works on every id', ~90% plain opinions), and truncation behavior ('never truncated, regardless of the `fields` mode'). It does not state error behavior for an invalid or nonexistent id, and read-only status is only implied by 'Fetch'/'read half' rather than declared.

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 the core purpose and structured around contrast with `report` and the inline-fields case, using a bold warning marker to flag the main confusion risk. It is a touch dense with backticked identifiers and parenthetical asides, but each sentence contributes disambiguation rather than filler.

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?

There is no output schema, and the description compensates by enumerating the return contents and guaranteeing non-truncation. For a single-required-parameter read tool, an agent has everything needed: what it returns, which ids are valid, its cost, and when not to call it.

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%, so `view_id`'s format is already documented; the description still adds meaning by asserting every id from `views` is valid, including the ~90% that are not archived reports, which the schema does not say. The generic envelope parameters (`_jq`, `_spill`, `_max_bytes`) go unmentioned, but they are self-documented.

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?

Opens with a specific verb and resource ('Fetch one analyst view by id') and immediately frames it as 'the read half of list→read', which positions it against the `views` list. It also names the exact payload returned (full body, AI summary, images, tagged securities), so the agent knows what it gets without opening a 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 trigger ('when a `views` list row is not enough', 'any id from `views`'), an explicit exclusion ('If the list row already carries what you need, do not call this — a `views` page at `fields=full` has the body inline'), and an explicit alternative ('This is not `report`') with the condition that selects the alternative (`full_text_available=true`). Nothing is left to inference.

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