Skip to main content
Glama

NEM Explorer (ScadaMiner)

start_question

Register the user question you're about to answer. Returns a question_id (UUID). Pass that question_id as an argument on every subsequent tool call in this answer turn — the server will cluster those calls into one auditable trace. Optional but recommended; tool calls without question_id still work but receive a one-line reminder.

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": {
      "question": "<question>"
    },
    "name": "start_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYesThe natural-language question you are about to answer. Stored verbatim so the resulting trace can be reviewed; do not include system prompts or scaffolding.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: the server clusters tagged calls into one auditable trace, and untagged calls trigger a reminder. It does not state whether repeated calls create separate traces (relevant since idempotentHint=false), which keeps it from a 5.

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?

Front-loaded with the action and return value, then the follow-up protocol. Three tight sentences, no filler, and the optionality caveat is placed where it matters.

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?

For a one-parameter tool with no output schema, the description covers the action, the returned identifier, and the cross-call contract needed to use it correctly. Nothing an agent needs is missing.

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 is fully documented in-schema, so baseline 3 applies. The description reinforces the intent of `question` but adds no format or constraint detail beyond what the schema says.

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 ('Register the user question you're about to answer') plus the return value (`question_id` UUID). No sibling tool does this, and the description makes its unique role unmistakable.

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?

Explicitly frames usage as 'Optional but recommended' and states the exact mechanics: pass the question_id on every subsequent call in this answer turn. It even discloses the fallback behavior (calls without question_id still work but get a one-line reminder), leaving nothing to inference.

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.