Skip to main content
Glama
mcp-feature-test

mcp-feature-test

by linuxrrze

Submit Dialog Lab result (app-only)

dialog_lab_submit

Stores user answers submitted by the Dialog Lab UI so the MCP server can retain and inspect responses during feature testing.

Instructions

Called by the Dialog Lab UI to store the user's answers. Hidden from the model.

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": {
      "data": "<data>"
    },
    "name": "dialog_lab_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the important behavioral trait that this is an app-invoked, model-hidden write path, but says nothing about what happens to the stored answers, whether it is idempotent, or what a call returns.

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?

Two short sentences with zero padding, and the invocation context is front-loaded before the audience restriction. Nothing is redundant.

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?

For a low-complexity, app-only handler that the model is told not to call, the description covers what an agent actually needs: what it does and that it is off-limits. The only gap is the opaque payload shape, which is largely irrelevant if the model never invokes it.

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 coverage is 0% for the single 'data' parameter, which is an open nested object with additionalProperties and no field documentation. The description only hints that it holds 'the user's answers', leaving the structure and required keys entirely unspecified.

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 names a specific verb and resource ('store the user's answers') and scopes it to the Dialog Lab UI, which clearly distinguishes it from the general dialog_lab_* siblings. It stops short of naming an alternative or explaining the result-side tools, but the core purpose is unambiguous.

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

Usage Guidelines4/5

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

'Hidden from the model' is an explicit when-not-to-use directive, which is exactly the guidance an agent needs to avoid calling it. It lacks a pointer to what the agent should use instead, but the exclusion itself is clear and actionable.

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