MCP Queen

Submit Field Report

submit_feedback

Submit a field report about an MCP server you have actually used (what worked, what failed, surprising behavior). Reports are quarantined for human review and never auto-published.

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": {
      "server_name": "<server_name>",
      "report": "<report>"
    },
    "name": "submit_feedback"
  }
}

Input Schema

Name	Required	Description
`report`	Yes	The field report, 20-2000 chars, specific and factual
`agent_name`	No	Optional: which agent/client is reporting
`server_name`	Yes	Official registry name of the server the report is about

Output Schema

Name	Required	Description	Default
`status`	Yes
`message`	Yes
`server_name`	Yes
`safety_notice`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 8, 2026

addedOutput schema / properties / safety_notice
```
Added value: +{
+  "type": "string"
+}
```

changedOutput schema / required

Previous value: -[
-  "status",
-  "server_name",
-  "message"
-]New value: +[
+  "safety_notice",
+  "status",
+  "server_name",
+  "message"
+]

Changed1 schema field changedJul 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {
+    "message": {
+      "type": "string"
+    },
+    "server_name": {
+      "type": "string"
+    },
+    "status": {
+      "const": "quarantined",
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "server_name",
+    "message"
+  ],
+  "type": "object"
+}

First observedJul 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

The description adds important behavioral context beyond annotations: reports are 'quarantined for human review and never auto-published.' This informs the agent that submission does not lead to immediate public visibility, which is a useful non-obvious trait. No contradiction with annotations.

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?

The description is two sentences long, front-loaded with the action and resource, and ends with a clear behavioral disclaimer. Every word earns its place; no redundant or filler content.

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 simple submission tool with a provided output schema, the description is sufficient. It covers what the report is about, the submission action, and the quarantine behavior. It doesn't mention post-review outcomes, but that is not necessary given the output schema exists.

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 explains each parameter well (report, agent_name, server_name). The description does not add any param-specific details, but the existing schema coverage justifies a baseline score of 3.

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 clearly states a specific verb ('Submit') and resource ('field report'), and defines the scope ('about an MCP server you have actually used'). It distinguishes the tool from its siblings, which are all search/get operations, by focusing on reporting feedback.

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?

The description gives a clear condition for use: 'you have actually used' a server, implying this tool is for real experience, not hypotheticals. It doesn't explicitly mention alternatives, but the sibling tools are all read-only, making the intended context unambiguous.

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

All MCP Queen tools Inspect

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.