Skip to main content
Glama

Local MCP

by com.local-mcp
OverviewDiscussionsAdmin

Survey Respond

survey_respond

Shows or submits the short in-product survey Local MCP assigned to this machine. Called with NO arguments it returns the pending survey and, in clients that support MCP Apps, renders it as an interactive card the user answers directly — prefer this. To submit conversational answers instead, pass answers keyed by each question's id (single/scale = one value, multiple = an array of values): call once to PREVIEW, then again with confirm=true to record. Do NOT invent answers — if no human gave them (you're running autonomously), call survey_skip instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
answersNoAnswers keyed by question id. Single/scale = a value; multiple = an array.
confirmNoSet true to actually record the answers. Omit/false = preview only (nothing is stored).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
surveyNoThe pending survey (no-args call) — rendered by the MCP Apps card.
messageNo
previewNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / required
      Previous value: -[
-  "answers"
-]New value: +[]
    • addedOutput schema / properties / survey
      Added value: +{
+  "additionalProperties": true,
+  "description": "The pending survey (no-args call) — rendered by the MCP Apps card.",
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • addedInput schema / properties / confirm
      Added value: +{
+  "description": "Set true to actually record the answers. Omit/false = preview only (nothing is stored).",
+  "type": "boolean"
+}
    • addedOutput schema / properties / preview
      Added value: +{
+  "type": "boolean"
+}
  3. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the two-phase preview/record workflow, that preview stores nothing, and that confirm=true is required to record. It also adds a safety safeguard: 'Do NOT invent answers.' No contradiction exists with readOnlyHint=false or destructiveHint=false.

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?

The description is compact and front-loaded: purpose first, then invocation modes, then safety guidance. Every sentence contributes useful operational or exclusionary information without fluff.

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?

Given the rich annotations, output schema, and 100% schema coverage, the description is complete enough for an agent to invoke correctly in both modes and to avoid a harmful autonomous submission. It does not need to describe return values because an output schema exists.

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?

Schema coverage is 100%, so the baseline is 3; the description adds meaning by explaining the no-argument retrieval mode and the preview-then-confirm sequence. It restates some of the schema's `answers` type guidance, and it does not fully spell out how to discover question `id`s beyond the initial survey response, so it falls just short of a 5.

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?

The description opens with a specific verb and resource: it 'Shows or submits the short in-product survey Local MCP assigned to this machine.' It differentiates itself from the sibling survey_skip by explicitly naming that tool as the alternative when no human answers are available.

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?

It gives clear when-to-use guidance: call with no arguments to render the interactive card and 'prefer this,' or pass `answers` for conversational submission. It also states the when-not-to-use condition: if running autonomously with no human-provided answers, call survey_skip instead.

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

All Local MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources