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

report

Fetch the FULL research-report text behind a view (parsed long-form), for when the views summary is not enough. Only works on views where full_text_available=true (archived sell-side reports) — get those from views --report-only, do not guess a view_id. A 404 no_full_text means that one view is a plain opinion with no archived report; it does NOT mean the endpoint is unavailable or that no reports exist. Consumer pricing: 1 credit per PDF page, with no minimum or maximum document charge, per UTC day. Call format=quote first for free page_count and credit_cost; all subsequent outline/full reads share the same daily document charge. Unknown PDF page count blocks paid reads; unpaginated non-PDF documents cost 1. Two-step usage: default format=outline returns a few-KB heading map + total_chars + each heading's char_offset; then call format=full with offset (e.g. an outline char_offset) to read the body in pages — follow next_offset to page through large docs instead of pulling everything at once.

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

Input Schema

NameRequiredDescriptionDefault
_jqNoJMESPath,对 data 求值(写 items[*].id)
_spillNotrue=全量落盘,只回摘要与取数地址
formatNoquote=free page count and price; outline=heading map (default, charges document); full=body sliceoutline
offsetNofull mode: start char offset (use an outline char_offset)
_fieldsNo逗号分隔的直接字段;有 items 时投影每行,否则投影 data;外层字段或嵌套结构用 _jq
_intentNo用户原问题一句话,仅分析用,可留空
view_idYesView id from `views --report-only` items[].id (full_text_available=true)
max_charsNofull mode: max chars per page (hard cap 80000)
_max_bytesNo响应字节上限,默认约 50 KB
_max_bytes_modeNo正文超限处理,默认 truncate 保留前缀

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden and does so: it discloses credit pricing (1 credit per PDF page, per UTC day, no min/max), that unknown page counts block paid reads, that unpaginated non-PDF docs cost 1 credit, and that quote is free while outline/full share a daily document charge. It also explains error semantics (404 `no_full_text` is per-view, not endpoint-wide) and paging via `next_offset`.

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 the gating condition, then pricing, then the two-step workflow — a sensible order for a dense tool. It is long and a few clauses restate what the schema's enum descriptions already say (quote=free page count and price), so it is slightly over budget, but almost every sentence carries operational information.

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 10-parameter tool with no annotations and no output schema, the description covers prerequisites, cost model, error interpretation, and the paging loop, and even names the response fields an agent needs (total_chars, char_offset, next_offset). Nothing essential to calling it correctly appears to be missing.

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 each parameter is already documented individually; the description adds cross-parameter workflow meaning instead — that `format=quote` yields free page_count and credit_cost, that `offset` should be seeded from an outline `char_offset`, and that outline/full reads share one daily charge. That is real value beyond the schema, though it does not explain every param (e.g. max_chars and the _-prefixed plumbing fields are left to the schema).

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 the FULL research-report text behind a view, parsed long-form') and immediately scopes it against the sibling summary tool ('for when the `views` summary is not enough'). An agent can distinguish this from `views` without opening either 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 explicit preconditions ('only works on views where full_text_available=true'), the exact way to obtain valid inputs ('get those from `views --report-only`, do not guess a view_id'), and a recommended call order (quote first, then outline, then full with offset). It also pre-empts a likely misread of the 404 `no_full_text` error, which is precisely the kind of when-not guidance that prevents wasted calls.

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