Skip to main content
Glama

NEM Explorer (ScadaMiner)

list_results

Read-onlyIdempotent

List the scratch tables you have stored via store_result, with each table's qualified_name (use it in execute_sql), row count, size, and time_window (the range its rows cover). Compare those windows: tables that should share a period and do not are a sign one was stored over too narrow a range. Pass your question_id from start_question — the listing is scoped to it. Call this to recall what intermediates you've already built before re-querying the warehouse.

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_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
question_idNo**Required.** The UUID from a `start_question` call — lists the scratch tables stored under that question.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so safety is covered. The description adds genuine behavioral insight beyond that: results are scoped to a question_id, and comparing time_window values reveals tables stored over too narrow a range. It does not mention ordering, empty-result behavior, or limits on how many tables are returned.

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?

Purpose is front-loaded in the first clause, and the diagnostic hint about comparing time windows is a useful second beat. Four sentences is slightly long for one parameter, but nothing is redundant filler.

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

Completeness5/5

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

There is no output schema, so the description carries the return-shape burden, and it does: qualified_name, row count, size, time_window. Combined with the scoping rule and the follow-up tool to use, an agent has everything needed to call and interpret it.

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 100% and the single parameter already documents itself as the UUID from start_question. The description restates that and adds the consequence ('the listing is scoped to it'), which is marginal value over the schema rather than new semantics.

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 ('List the scratch tables you have stored via store_result') and enumerates the returned fields, qualified_name, row count, size, time_window. It is clearly distinct from siblings like list_tables or list_dashboards because it scopes to scratch tables created via store_result.

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 explicit when-to-use guidance ('Call this to recall what intermediates you've already built before re-querying the warehouse') and an implicit when-not (don't re-query the warehouse first). It also routes the agent forward: use the qualified_name in execute_sql and pass question_id from start_question.

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.