Skip to main content
Glama
Sign In

Umtri

by io.umtri
OverviewDiscussionsAdmin

List feedback filed about Umtri

list_feedback

Lists feedback filed about Umtri the product (see send_feedback) — not the bugs of any ground. Umtri operators only: every other account gets 403, so do not call this to check on feedback you filed. Newest first. Status: open (untouched) → done (handled) / wontfix (declined, with the reason in note). Defaults to every status; pass status to narrow. Use limit to bound a scan.

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

Input Schema

NameRequiredDescriptionDefault
kindNoFilter by kind. Omit for both.
limitNoReturn at most this many.
orderNoBy creation time. Default "desc" (newest first).
statusNoFilter by status. Omit for all.

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?

With no annotations, the description carries the whole burden and does well: it discloses the authorization requirement (403 for every non-operator account), the ordering (newest first), the default of returning all statuses, and the status lifecycle with note semantics. It stops short of describing the returned record structure, which leaves one gap for a tool with no 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense paragraph, front-loaded with the identity/scope statement before the access constraint and the operational hints. Every clause carries information an agent needs; there is no filler or redundant restatement of the schema.

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 four-parameter, all-optional read tool, the definition covers scope, access control, ordering, filtering defaults, and status semantics. With no output schema, only the shape of returned records is unaddressed, which is a minor omission.

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, but the description earns above that by explaining what the status values actually mean (open = untouched, done = handled, wontfix = declined with reason in note) — semantics the enum alone does not convey. It also reinforces the default and the narrowing role of status and limit.

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 names a specific verb and resource ('Lists feedback filed about Umtri the product') and immediately scopes it away from a confusion risk by pointing at send_feedback and stating 'not the bugs of any ground,' which separates it from sibling list_bugs.

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 an explicit exclusion ('Umtri operators only... do not call this to check on feedback you filed') and names the correct alternative for that case (send_feedback). It also advises passing status to narrow and limit to bound a scan, so both when-to-use and how-to-narrow are covered.

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

All Umtri 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