Skip to main content
Glama
deeptrue MCP

deeptrue MCP

Official
by deeptrue-ag

List report files

list_reports
Read-only

Retrieve report files for the active organization, with optional pagination and per-call organization selection, to browse available reports.

Instructions

List report files for the active organization.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_reports"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
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/5.0
Behavior3/5

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

Annotations already establish read-only and closed-world behavior. The description adds only the active-organization scope; it does not disclose pagination behavior, default page size, return shape, or how a per-call organization override changes the 'active organization' framing.

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 description is a single front-loaded sentence with no wasted wording. Its terseness contributes to the completeness gap, but as a conciseness and structure matter it is clean rather than bloated.

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 simple read-only list tool, the description identifies the resource and organization scope, which is enough to initiate a call. However, with no output schema and only 33% parameter description coverage, it omits pagination semantics and return expectations, so it is only minimally complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, with limit and offset undocumented in the schema. The description does not explain pagination or those parameters, nor does it clarify that the organization parameter can override the active organization for a single call, so it fails to compensate for the coverage gap.

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?

The description gives a specific verb ('List'), a specific resource ('report files'), and a scope ('for the active organization'), so an agent can distinguish this from a single-report fetch like get_report. It does not explicitly name a sibling or clarify boundaries with get_report_layouts, keeping it just below a 5.

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?

There is no when-to-use or when-not-to-use guidance, and no alternative tool is named. The only contextual cue is the active-organization scope; an agent must infer from the tool name alone that this is for enumerating report files rather than fetching or refreshing one.

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