WiseGrid MCP

run_report

Run a report and retrieve its rows with cursor-based pagination, handling up to 500 records per request.

Instructions

Run a report and return its rows, cursor-paginated. Max limit 500.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No
`report_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 2, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses that results are cursor-paginated and the maximum limit is 500, which is helpful. However, it does not state whether running a report has side effects, requires any special permissions, or how errors are handled.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that front-loads the primary purpose and then provides key pagination details. No unnecessary words or repetitions.

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?

Given the presence of an output schema, return values are already documented. The description covers the core purpose, pagination behavior, and limit cap, which are sufficient for invoking the tool. It could mention usage relative to sibling tools or error conditions, but for a simple 3-parameter tool, it is reasonably complete.

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 compensate. It adds meaning for 'limit' (max 500) and 'cursor' (pagination token), but 'report_id' is not explicitly described. The name is fairly obvious, and the description partially covers the parameters, but not fully.

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 clearly states the tool's purpose: 'Run a report and return its rows.' It uses a strong verb ('run') and specifies the resource ('report') and output ('rows'). This distinguishes it from sibling tools like get_report (likely metadata) and list_reports (listing reports).

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

Usage Guidelines3/5

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

The description implies usage when you have a report_id and want to retrieve data rows, but it does not explicitly mention when to use this tool over alternatives or provide exclusions. It lacks a direct reference to sibling tools like get_report for metadata-only needs.

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

Deploy Server