Skip to main content
Glama

Send feedback to the website

send_feedback

Use this when a task on minipacs.net is done or abandoned, to tell the site's team how it went: what worked, what was missing or wrong. Returns received: true once stored.

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": {
      "outcome": "<outcome>"
    },
    "name": "send_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoThe page URL or path the feedback is about.
taskNoWhat you were trying to do on the site, up to 500 characters.
detailNoWhat worked and what was missing or wrong, up to 2000 characters.
outcomeYesHow the task went: success, partial or failure.

Output Schema

NameRequiredDescriptionDefault
receivedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / detail / description
      Added value: +"What worked and what was missing or wrong, up to 2000 characters."
    • addedInput schema / properties / outcome / description
      Added value: +"How the task went: success, partial or failure."
    • addedInput schema / properties / page / description
      Added value: +"The page URL or path the feedback is about."
    • addedInput schema / properties / task / description
      Added value: +"What you were trying to do on the site, up to 500 characters."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "received": {
      +      "const": true,
      +      "type": "boolean"
      +    }
      +  },
      +  "required": [
      +    "received"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish that this is a non-read-only, non-destructive write with no idempotency guarantee. The description adds useful context about the destination (the site's team) and that the data is stored, but it says nothing about duplicate submissions, auth requirements, or rate limits, and the 'received: true' line largely restates the output schema.

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 front-loaded sentence leads with the trigger condition and then the payload content, with no filler. The trailing return-value note is minor and arguably redundant given the output schema.

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?

With a full output schema, complete parameter documentation, and annotations covering the safety profile, a short description suffices. The only real gap is guidance on repeated submission behavior for a non-idempotent tool.

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% with every parameter documented, including the outcome enum, so the schema does the heavy lifting. The description reinforces the intent of the detail field but adds no format or constraint detail beyond the schema.

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 action (send feedback about a task on minipacs.net) and the content it should carry (what worked, what was missing or wrong). The purpose is unambiguous and distinct from a question-asking sibling, 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 Guidelines4/5

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

It gives a clear trigger condition: 'when a task on minipacs.net is done or abandoned.' That is actionable context, but there is no explicit when-not guidance or reference to an alternative tool for adjacent needs.

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