Skip to main content
Glama

feedback

End-user app feedback sent to the project's private owner inbox (destination: "project_owner_inbox") — this does not reach the Somewhere platform team. Every successful submission repeats that destination and names the exact platform-support calls. Submit: provide a message about that project's own UI or behavior. List: without message it returns feedback on a project you own. When the project owner resolves one of these reports, the owner-facing project channel can emit a feedback_resolved event.

Platform bugs, missing capabilities, deploy/API problems and documentation issues are out of scope for this tool. support_ticket({ message: "..." }) sends such a report to the platform support queue.

Example:

// Submit:
{ "project_id": "my-saas", "message": "The checkout button in this app does nothing after I enter my card" }

// List:
{ "project_id": "my-saas" }

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": {
      "project_id": "<project_id>"
    },
    "name": "feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageNoFeedback message. Omitted: feedback is listed instead.
page_urlNoOptional page URL the feedback is about (submit mode)
project_idYesProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, idempotentHint=false; the description adds the material behavior that submissions land in the project owner's private inbox rather than the platform team, and that a resolved report can emit a `feedback_resolved` event downstream. That is real behavioral context beyond the structured fields. It stops short of noting that the list mode is a read while the submit mode is a write, which would have helped given the mixed readOnly profile.

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?

Front-loaded with destination and scope, then modes, then exclusions, then a compact JSON example, which is a sensible order. The sentence "Every successful submission repeats that destination and names the exact platform-support calls" is slightly opaque and could be trimmed or sharpened, but overall the text earns its space.

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 three-parameter, dual-mode tool with no output schema, the description covers destination, mode selection, exclusions, the alternative tool, and the downstream event. What is thin is what list mode actually returns (shape or volume of the feedback records) and whether pagination exists, which an agent would want before calling it blind.

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%, so message, page_url, and project_id are already documented, including the mode-switch meaning of an omitted message and the default/slug resolution behavior. The description adds only reinforcement of the message-presence semantics and a worked example, not new meaning. Baseline 3 applies when the schema carries the parameter burden.

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 opening sentence names the resource (end-user app feedback), its destination (the project's private owner inbox), and what it is not (it does not reach the Somewhere platform team). The submit-vs-list duality is stated with the exact trigger (message present or absent), so an agent can tell it apart from support_ticket without opening either schema.

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 when-to-use for both modes ("Submit: provide a message about that project's own UI or behavior"; "List: without message it returns feedback on a project you own") plus an explicit when-not-to-use list of out-of-scope cases (platform bugs, missing capabilities, deploy/API, documentation). It names the concrete alternative, `support_ticket({ message: "..." })`, and the reason it is the right alternative.

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