Equity Research Pilot

research_explore_report

Read-onlyIdempotent

Progressively explain the SAME frozen report, without new data, recalculation or AI calls.

    Omit topic for the topic directory. Supply topic for an item index; add item_id for its full detail.
    Follow returned refs with topic=evidence and item_id=the exact ref. No arbitrary file access.
    Content is paginated JSON TEXT: join Unicode character pages using next_offset before parsing.
    Preserve report_id, source dates, missing/conflicting evidence and conditions in explanations.
    To change assumptions, precheck and explicitly start a new analysis instead.

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": {
      "project_id": "<project_id>",
      "report_id": "<report_id>"
    },
    "name": "research_explore_report"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`topic`	No
`offset`	No
`item_id`	No
`report_id`	Yes
`project_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, and the description adds behavior beyond them: the report is frozen, no recalculation or AI calls occur, arbitrary file access is refused, and content arrives as paginated JSON text that must be joined via next_offset before parsing. That pagination warning is a real operational hazard the annotations do not cover.

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?

The opening sentence front-loads the core constraint and the following lines are each a distinct rule with no filler. Slightly dense and line-broken rather than prose, but every sentence earns its place.

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?

An output schema exists, so return values need not be described, and the description still covers the one return-side trap (paginated text needing next_offset). The remaining gap is the unexplained limit/offset/project_id parameters, which matters for a tool whose whole purpose is paging through content.

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 0%, so the description must carry the load. It explains the topic/item_id relationship well, but says nothing about limit, offset, project_id or report_id, and the enum values for topic are only partially surfaced (evidence is named, the other seven are not). Partial compensation for a six-parameter 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?

The description states a specific verb and resource ('progressively explain the SAME frozen report') and immediately bounds the scope with 'without new data, recalculation or AI calls', which separates it from research_get_report and research_replay_report. An agent can tell what this tool does and what it does not do without 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?

It gives an explicit navigation protocol: omit topic for the directory, supply topic for an item index, add item_id for full detail, and follow refs with topic=evidence plus the exact ref. It also names the alternative path for a different goal ('to change assumptions, precheck and explicitly start a new analysis instead'), which is exactly the when-not guidance an agent needs.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Equity Research Pilot tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?