Skip to main content
Glama

report_feedback

Report a problem to viaSocket while building with it: an error, a confusion, wrong docs or skills, a user correction, or a missing capability. Problems only, never success; no need to ask the user; a failed report never stops the task. Plugs: fix or extend the user's own plugs (the ones in list_plugins) yourself, and build a plug for an app that has none. A plug used in flows but not in list_plugins is viaSocket's: never edit it, report it here (refs.pluginId, refs.actionId; a missing action, trigger or field is kind missing_capability, with exactly what is needed and why). Body: source (sdk | http_api | plug | action | trigger | connection | skill | other), kind (error | confusion | missing_capability | wrong_instructions | user_correction) and feedback (what happened, in plain words), plus optional severity, stage, intent, attempted, expected, actual, error, refs, env and retries. Never include secrets, tokens or script_id. The org and user come from the sign-in. It answers { success, requestId, status, message }: for a missing capability keep the requestId next to the unwired part and check it later with get_request_status.

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

Input Schema

NameRequiredDescriptionDefault
envNoe.g. {"sdkVersion":"0.7.0","framework":"nextjs","language":"typescript","client":"claude-code"}
kindNoe.g. error
refsNoe.g. {"app":"slack","pluginId":"rowslack123","actionId":"rowsendmsg01","requestId":"req_abc"}
errorNoe.g. {"status":500,"code":"INTERNAL","message":"failed"}
stageNoe.g. actions_and_events
actualNoe.g. 500 INTERNAL
intentNoe.g. Post to a Slack channel when an order is created
sourceNoe.g. action
retriesNoe.g. 2
expectedNoe.g. Message posted
feedbackNoe.g. Slack Send Message returns 500 on valid input; same call worked yesterday
severityNoe.g. degraded
attemptedNoe.g. Ran Send Message with channel and text from the document's sample

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations only declare the non-read-only, non-destructive, non-idempotent profile; the description adds real behavioral context the annotations cannot: a failed report never stops the task, no user confirmation is required, org and user are derived from sign-in, and it names the response shape { success, requestId, status, message }. It also discloses the confidentiality constraint ("Never include secrets, tokens or script_id"), which is a genuine operational rule rather than a restatement.

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 and the success/never-success rule are front-loaded, and no sentence is filler. The middle "Plugs:" sentence is dense and parenthesis-heavy, forcing the reader to unpack three distinct rules in one clause, which costs some scanability despite the tight word budget.

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 13-parameter, nested-object tool with no output schema, the description covers the classification taxonomy, the refs convention, confidentiality limits, failure behavior, and the return payload including how to follow up on a requestId. An agent can call it correctly and act on the result without any other source.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is nominally 100%, but the schema only supplies "e.g." samples and no enum constraints (0 enums across 13 params). The description supplies the actual allowed values for source (sdk | http_api | plug | action | trigger | connection | skill | other) and kind (error | confusion | missing_capability | wrong_instructions | user_correction), plus concrete semantics for refs (pluginId/actionId) and the rule that a missing action/trigger/field maps to kind missing_capability with what is needed and why. That is meaningful meaning added beyond the schema.

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?

"Report a problem to viaSocket while building with it" states a specific verb and resource, then enumerates exactly what counts as a problem (error, confusion, wrong docs or skills, user correction, missing capability). This clearly separates it from siblings like get_request_status (checking a request) and report_published (success reporting).

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?

Explicit exclusions ("Problems only, never success"), explicit permission ("no need to ask the user"), and explicit alternatives ("fix or extend the user's own plugs yourself, and build a plug for an app that has none"; a viaSocket-owned plug must be reported here, never edited). It also routes the missing-capability follow-up to get_request_status by name, which is the right sibling.

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.

Resources