Smartsheet Audit (x402)

leave_feedback

Free. Tell us why you did not pay for audit_smartsheet (or other feedback). Preferred reason values: price_too_high, no_wallet, input_format, not_needed, other (unknown values stored as other). Also accepts feedback/comment/text fields. Message truncated to 500 chars.

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

Input Schema

Name	Required	Description
`text`	No	Alias for message
`agent`	No	Optional agent or client name
`reason`	No	Preferred: price_too_high, no_wallet, input_format, not_needed, other. Other values mapped to other.
`comment`	No	Alias for message
`message`	No	Optional short note
`feedback`	No	Alias for message

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedNov 6, 2026

changedInput schema / properties / agent / description

Previous value: -"Optional agent or client name (max 80 chars)"New value: +"Optional agent or client name"

removedInput schema / properties / agent / maxLength
```
Removed value: -80
```

addedInput schema / properties / comment

Added value: +{
+  "description": "Alias for message",
+  "type": "string"
+}

addedInput schema / properties / feedback

Added value: +{
+  "description": "Alias for message",
+  "type": "string"
+}

changedInput schema / properties / message / description

Previous value: -"Optional short note (max 500 chars). No secrets."New value: +"Optional short note"

removedInput schema / properties / message / maxLength
```
Removed value: -500
```

changedInput schema / properties / reason / description

Previous value: -"Why you stopped / feedback category: price_too_high, no_wallet, input_format, not_needed, other"New value: +"Preferred: price_too_high, no_wallet, input_format, not_needed, other. Other values mapped to other."

removedInput schema / properties / reason / enum

Removed value: -[
-  "price_too_high",
-  "no_wallet",
-  "input_format",
-  "not_needed",
-  "other"
-]

addedInput schema / properties / text

Added value: +{
+  "description": "Alias for message",
+  "type": "string"
+}

removedInput schema / required
```
Removed value: -[
-  "reason"
-]
```

AddedNov 5, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The description adds real behavior beyond the annotations: submission is free, messages are silently truncated to 500 characters, and unrecognized reason values are coerced to "other" rather than rejected. That truncation-and-coercion detail is exactly the kind of information an agent cannot infer from readOnlyHint=false and openWorldHint=false. It stops short of saying who receives the feedback or whether the call returns anything.

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?

Three compact sentences with no wasted filler, and the most decision-relevant facts (free, purpose, truncation limit) are front-loaded. The reason-enumeration sentence duplicates schema content and is the one piece that could be cut or condensed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter, all-optional write tool with full schema coverage and no output schema, the description covers purpose, cost, and truncation, which is close to sufficient. It leaves open what happens after submission — whether feedback is stored anonymously, who sees it, and what the call returns — which matters for an agent deciding whether to invoke a write.

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 both the alias fields (text/comment/feedback) and the reason values are already documented in the schema, and the description largely restates them. It does add the 500-character truncation limit for the message field, which is not in the schema, but otherwise adds little meaning beyond structured data — the baseline 3 for full coverage 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?

The description uses a specific verb+resource framing ("Tell us why you did not pay for audit_smartsheet (or other feedback)") and names the sibling tool audit_smartsheet as the thing feedback is about, so an agent can distinguish this from audit_preview and audit_smartsheet. The parenthetical "(or other feedback)" slightly blurs the scope but does not obscure the core purpose of submitting feedback.

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?

"Free" plus "why you did not pay" implies the trigger context (user declined a paid audit, or has general feedback), which is a useful hint. However, there is no explicit when-to-use/when-not guidance, no statement that this should not be called for successful audits, and no mention of whether a user must consent before their feedback is sent.

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

All Smartsheet Audit (x402) 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.

Resources

Need Help?