Skip to main content
Glama

NEM Explorer (ScadaMiner)

fetch_result_rows

Read-onlyIdempotent

Page through a parked query result by its result_id (returned by execute_sql when a result exceeds the inline preview). Reads the stored snapshot — the exact rows the preview described, at zero warehouse cost and with no re-execution drift. Use this ONLY when you need to see specific raw rows beyond the preview; if what you actually want is a different aggregation or filter, write new SQL instead — it is cheaper and better. A page is capped at 20 KB as well as 1000 rows, so it can return fewer than limit: always continue from next_offset, never offset + limit. Handles expire after 24 hours; an expired id means re-running the SQL for a fresh one.

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": {
      "result_id": "<result_id>"
    },
    "name": "fetch_result_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoRows to return, max 1000. Defaults to 100. A page is also capped by size, so it can return fewer: always continue from `next_offset`.
offsetNoFirst row to return (0-based). Defaults to 0.
result_idYesThe `result_id` an `execute_sql` response returned.
question_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds substantial context beyond them: zero warehouse cost, no re-execution drift, a dual page cap of 20 KB and 1000 rows, mandatory continuation via `next_offset`, and a 24-hour handle expiry with the recovery path.

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-loads the core action, then attaches cost/expiry/page-cap caveats, each in a compact clause. It is slightly dense but every sentence carries operational information; nothing is filler.

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?

No output schema exists, and the description covers the return-side essentials an agent needs — page size behavior, `next_offset` continuation, and handle lifetime — though it never sketches the response shape or explains `question_id`.

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?

With 75% schema coverage the schema already documents `limit`, `offset` and `result_id`; the description adds the crucial non-obvious semantics that a page may return fewer than `limit` due to the byte cap and that callers must advance using `next_offset` rather than offset arithmetic. It leaves `question_id` unexplained in both places.

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 — paging a parked query result by `result_id` — and ties it to the originating `execute_sql` response, which distinguishes it from siblings like `execute_sql` or `list_results`.

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 an explicit when-to-use condition ('ONLY when you need to see specific raw rows beyond the preview') and names the concrete alternative behavior ('write new SQL instead — it is cheaper and better'), so the agent knows both the trigger and the exclusion.

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.