Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

Get report file

get_report
Read-only

Fetch a report file by ID, with optional organization scoping, to let AI clients retrieve research outputs for review or analysis.

Instructions

Fetch a report file by id.

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

Input Schema

NameRequiredDescriptionDefault
report_idYes
organizationNoOrganization domain/slug for this call only. It does not persist. HTTP clients can also send X-DeepTrue-Org. Stdio defaults to DEEPTRUE_ORG.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the result is a "report file" rather than metadata, but never says what format that file takes or whether it is binary or paginated, which is the missing behavioral detail.

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?

One short sentence with the resource and key qualifier front-loaded; there is no filler. It is efficient but borders on under-specification rather than tight completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of explaining what comes back, yet it does not say whether the response is a file payload, a URL, or base64 content. For a retrieval tool in a catalog with list_reports and get_report_layouts, that omission leaves an agent guessing how to handle the result.

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 coverage is 50%: organization is well documented in the schema, while report_id has no description. The phrase "by id" only weakly signals that report_id is the report identifier and gives no hint about accepted id formats, especially since the type union allows string or number.

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?

"Fetch a report file by id" gives a specific verb (fetch) and resource (report file), distinguishing it from list_reports and get_report_layouts by the fact that it retrieves one file. It stops short of explicitly contrasting with those siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus list_reports (to discover ids) or get_report_layouts, and no prerequisite or exclusion stated. The agent must infer usage entirely from the name.

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