AgentMart

Send feedback

send_feedback

Tell us something, in plain words: a wish (what you would rather buy than build, with would_pay_cents), a pain_point, a competitor you used and what it did better, an improvement, a bug (in something your owner bought: pass order_id, our own records and re-runs decide, never a report alone; on a public page or in the API: no order_id, pass page_url when it is about a page; any bug needs a passport with an owner), or praise. Up to 1000 characters; no links, code, contact details or secrets. Answering the question in whoami? Pass its prompt_id. We read every message; my_feedback shows our answer.

Input Schema

Name	Required	Description
`item`	No	Item slug, when it is about one item.
`text`	Yes	Your message in plain words, up to 1000 characters after cleanup.
`type`	Yes	What kind of message this is.
`order_id`	No	Your owner's order, when a bug is about something your owner bought. Leave it out for a bug on a public page or in the API.
`page_url`	No	type bug only: the https address of the page the bug is on (at most 2048 characters, no key or token in it).
`prompt_id`	No	The prompt_id of the question in whoami, when you answer it.
`competitor`	No	type competitor only.
`passport_token`	No	Your amp_ token, only if you have no app sign-in and cannot send a header.
`would_pay_cents`	No	type wish only: what it would be worth to you.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 23, 2026

addedInput schema / examples

Added value: +[
+  {
+    "text": "A way to pause one uptime check without removing it.",
+    "type": "improvement"
+  }
+]

changedInput schema / properties / passport_token / description

Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."

Changed4 schema fields changedOct 13, 2026

removedInput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

changedInput schema / properties / passport_token / description

Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."

addedInput schema / properties / passport_token / maxLength
```
Added value: +200
```
removedInput schema / properties / passport_token / pattern
```
Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
```

Changed2 schema fields changedOct 6, 2026

changedInput schema / properties / order_id / description

Previous value: -"Your owner's order. Required for type bug."New value: +"Your owner's order, when a bug is about something your owner bought. Leave it out for a bug on a public page or in the API."

addedInput schema / properties / page_url

Added value: +{
+  "description": "type bug only: the https address of the page the bug is on (at most 2048 characters, no key or token in it).",
+  "maxLength": 2048,
+  "minLength": 1,
+  "type": "string"
+}

Changed7 schema fields changedOct 5, 2026

addedInput schema / additionalProperties
```
Added value: +false
```
addedInput schema / properties / competitor / additionalProperties
```
Added value: +false
```
addedInput schema / properties / competitor / properties / name / description
```
Added value: +"Its name."
```
addedInput schema / properties / competitor / properties / what_they_do_better / description
```
Added value: +"What it did better."
```

changedInput schema / properties / passport_token / description

Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."

addedInput schema / properties / text / description

Added value: +"Your message in plain words, up to 1000 characters after cleanup."

addedInput schema / properties / type / description
```
Added value: +"What kind of message this is."
```

First observedOct 4, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The description adds meaningful behavior beyond the annotations: a 1000-character limit after cleanup, a ban on links/code/contact details/secrets, bug evidence requirements, and the fact that messages are read with responses available via my_feedback. Annotations already cover safety and idempotency, but the description does not discuss authentication or privacy beyond the bug passport requirement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is information-dense but written as one long, heavily parenthetical sentence that is difficult to parse. It is appropriately sized for the tool's complexity, but the structure could be clearer and more front-loaded.

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 complex tool with nine parameters, a nested competitor object, and no output schema, the description covers the main type-specific routing and constraints an agent needs. It does not explain every parameter (e.g., item) or the full response flow, but the schema descriptions cover those details.

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 adds valuable conditional semantics: would_pay_cents applies to wishes, competitor applies to competitor feedback, order_id versus page_url depends on bug context, and prompt_id applies when answering a whoami question. It still leaves some parameter interactions implicit, such as the role of item.

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?

The description names the action clearly ('Tell us something') and enumerates the feedback categories: wish, pain_point, competitor, improvement, bug, and praise. It also references related tools (whoami and my_feedback), though it does not explicitly distinguish send_feedback from the sibling make_wish for wish-type submissions.

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?

It gives detailed conditions for each feedback type, including when to pass order_id versus page_url for bugs and when to pass a prompt_id for a whoami question. It does not state when not to use this tool or name alternative siblings, so it falls short of the top score.

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

All AgentMart 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.

Send feedback

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources