mcphost

host.feedback.list

List your own feedback (newest first, status received). Anonymous callers get [].

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max rows, up to 100; default 20.
`tenant_key`	No	The key `signup` returned. Optional on the connection that ran signup (or host.redeem): that connection is already bound to the tenant it created, so later calls on it need no tenant_key. On a connection with no Authorization: Bearer header and no prior signup, omitting it implicitly signs that connection up as a brand-new tenant and runs this call as it -- see host.whoami's source field. When both a header and this argument are present, the header wins.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`count`	Yes
`feedback`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 16, 2026
- removedOutput schema / properties / feedback / items / properties / context / type
```
Removed value: -"null"
```
- changedOutput schema / properties / note / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

Changed1 schema field changedOct 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "type": "integer"
+    },
+    "feedback": {
+      "items": {
+        "properties": {
+          "context": {
+            "type": "null"
+          },
+          "created_unix": {
+            "type": "integer"
+          },
+          "feedback_id": {
+            "type": "string"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "last_call_ids": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "status": {
+            "type": "string"
+          },
+          "text": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "context",
+          "created_unix",
+          "feedback_id",
+          "kind",
+          "last_call_ids",
+          "status",
+          "text"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "note": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "count",
+    "feedback"
+  ],
+  "type": "object"
+}

AddedOct 12, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose ordering (newest first), an implicit status filter (received), and the anonymous-caller result ([]), which is real behavioral value. It omits auth/permission requirements and rate limits, so a 3 is appropriate.

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 tight sentence, front-loaded with the verb and resource and parenthesized with ordering/filter qualifiers. No wasted words.

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 format need not be explained. The description covers scope, ordering, filter, and the anonymous edge case, leaving only minor details like pagination semantics to the schema.

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 both optional parameters including the tenant_key fallback behavior. The description adds no parameter detail, so the baseline 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 (List) and resource (your own feedback), plus scoping ('your own') that implicitly separates it from host.feedback.send. It does not explicitly name a sibling alternative, so it stops short of a 5.

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 'Anonymous callers get []' clause gives a when-not condition, which is useful. However, there is no explicit when-to-use framing or named alternative (e.g., host.feedback.send), so usage is only implied.

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

All mcphost tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.