Skip to main content
Glama
mcp-feature-test

mcp-feature-test

by linuxrrze

Read Dialog Lab results

dialog_lab_results
Read-only

Fetches what users submitted in the Dialog Lab graphical dialog, most recent entry first. Use it to review captured responses, with a limit parameter to control how many results are returned.

Instructions

Return what users submitted in the Dialog Lab graphical dialog (most recent first).

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior3/5

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

The readOnlyHint annotation already declares the safety profile, so the description only adds the ordering behavior ('most recent first') and the notion that the content originated from user submissions. It does not disclose return shape, whether results span all sessions, or how the limit interacts with ordering.

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?

A single compact sentence with the key information front-loaded and zero padding. 'What users submitted' is slightly loose where 'submitted responses' would be tighter, but nothing is wasted.

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 one-parameter read tool with annotations and no output schema, the definition covers purpose and ordering but leaves the return structure undefined. An agent cannot tell what a result entry looks like or whether all submitted fields are included.

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 0% and the description never mentions the single 'limit' parameter, so no meaning is added beyond the schema's name, default of 3, and 1-50 bounds. The schema constrains the value but the description does not explain whether the limit applies before or after ordering.

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 states a specific verb and resource: 'Return what users submitted in the Dialog Lab graphical dialog,' plus an ordering guarantee ('most recent first'). That read/retrieve framing implicitly contrasts with the write-oriented sibling dialog_lab_submit, though no sibling is named explicitly.

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?

Usage is only implied by the read wording and the shared 'dialog_lab_' prefix; there is no explicit when-to-use or when-not guidance relative to dialog_lab_submit or open_dialog_lab. An agent can infer this is the retrieval side, but the definition does not say so.

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