Skip to main content
Glama

feedback

Send feedback about printsi: what worked, what didn't, what you wish it did. Goes straight to the people building it.

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

Input Schema

NameRequiredDescriptionDefault
orderNoThe order it's about (ord_…), if any.
ratingNoOptional 1–5.
messageYesThe feedback (10–4000 characters).

Output Schema

NameRequiredDescriptionDefault
okYes
dataNo
errorNo
summaryNo
warningsNo
next_actionsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false, so the agent knows this is a non-destructive external write. 'Goes straight to the people building it' usefully confirms the message reaches a human team and implies a one-way submission with no reply, but nothing is said about attribution, anonymity, rate limits, or whether repeat submissions are deduplicated.

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?

Two short sentences, front-loaded with the action and resource, with the delivery detail as a supporting second sentence. No filler or redundancy.

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?

An output schema exists, so return values need no explanation, and the tool is a simple three-parameter submission. The remaining gap is the absence of any disambiguation from ticket_create and no statement of what happens after submission (confirmation, follow-up).

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 description coverage is 100%, so the schema already documents order, rating, and message including length bounds. The description's 'what worked, what didn't' loosely characterizes the message body but adds nothing about the optional order or rating parameters, so the baseline of 3 applies.

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?

States a specific verb and resource ('Send feedback about printsi') and even enumerates the kinds of content expected ('what worked, what didn't, what you wish it did'). It is clear on its own, but it never distinguishes itself from the sibling ticket_create, which an agent could plausibly confuse with feedback submission.

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

Usage Guidelines3/5

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

The phrasing implies the situation (you have an opinion about the product to relay) but gives no explicit when-to-use or when-not guidance, and no routing to alternatives such as ticket_create for problems that need a tracked resolution. Usage is inferable rather than stated.

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