mcphost

host.feedback.send

Tell the host's humans what you needed: kind, up to 2048 bytes of text, optional context. Works before signup. Returns feedback_id.

Input Schema

TableJSON Schema

Name	Required	Description
`kind`	Yes	What you are telling the host.
`text`	Yes	What you needed or saw; 1 to 2048 bytes after trim.
`context`	No	Optional, at most 1 KB: tool, error_code, free.
`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
`kind`	Yes
`feedback_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "feedback_id": {
+      "type": "string"
+    },
+    "kind": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "feedback_id",
+    "kind"
+  ],
+  "type": "object"
+}

AddedOct 12, 2026

TDQS

A3.5/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 discloses that the tool is auth-independent ('works before signup') and returns a feedback_id, which is useful. It does not cover the significant implicit behavior documented in the schema (omitting tenant_key on an unauthenticated connection silently signs up a new tenant), leaving that to structured data.

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?

Two dense sentences with the payload and the key behavioral fact (pre-signup availability) front-loaded; every clause carries information and nothing is padded.

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 4-parameter tool with a full output schema, the description covers purpose, payload, availability, and return value. The remaining complexity (tenant_key/implicit signup) is handled by the very detailed schema and need not be repeated.

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 kind, text, context, and the nuanced tenant_key semantics. The description only restates the 2048-byte limit and the optionality of context, adding essentially nothing beyond structured fields.

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 action and resource: sending feedback to the host's humans, with the payload shape (kind, text, context) named up front. It implicitly distinguishes itself from host.feedback.list via 'Tell ... what you needed', though it does not name any sibling.

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?

'Works before signup' is a real usage qualifier that tells the agent this call is available pre-auth. However, it gives no guidance on when to send feedback versus reaching for host.help.search or host.feedback.list, and no explicit exclusions.

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.