Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Send Feedback to Meshive

send_feedback

Report a bug, idea or complaint to the Meshive team: preview the feedback first, then send it only after the user agrees.

Instructions

Send a bug report, an idea or a complaint to the Meshive team, as the console's Send feedback does. When to offer it: a Meshive tool failed unexpectedly (code server_error, or an error that isn't a JSON object with code, message and next_step), or the user says something about Meshive is broken, confusing or missing. Then ask the user once whether to send it to Meshive, at most once per conversation, and only send it if they say yes. Don't offer it for errors whose next_step already explains them (rate limits, credit, a wrong id, a refused request), and never send one the user didn't agree to. summary is one line under 200 characters. details (optional) says, in your own words, what the user did, what they expected and what happened; summary and details together stay under 4000 characters. kind is bug, idea or complaint. For a failed call, tool is that tool's name and error_code its code (plain lowercase identifiers; anything else is left out). Never put passwords, API or access keys, tokens, environment values, log or command output, file contents, or workspace, pod, storage and other resource names or ids in the text; describe the problem instead. With confirm=false (default) it returns exactly what would be sent and sends nothing: show it to the user, and call again with confirm=true only after they agree. Don't promise a reward, credit or a reply: say only that the team reviews every report. Every write requires operation_id. Reuse the ID returned by the preview, or generate a UUID before the first call. Keep it for confirmation and all retries; a new ID means a new operation. After a timeout, check operation_status and resource state before retrying.

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": {
      "summary": "<summary>"
    },
    "name": "send_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
toolNo
confirmNo
detailsNo
summaryYes
error_codeNo
operation_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.10.0

TDQS

A4.9/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that confirm=false is a dry-run returning exactly what would be sent, that operation_id must be reused across preview/confirm/retries, and that a new ID means a new operation. It also adds a privacy contract (no passwords, keys, tokens, env values, logs, file contents, or resource names/ids) and a tone constraint (don't promise rewards, credit or replies) that no annotation conveys.

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?

Front-loaded with purpose then a "When to offer it" block, and the parameter and safety rules are grouped logically. It is long, and the closing paragraph on operation_id/retry reads as generic boilerplate appended to the tool-specific content, which slightly dilutes the otherwise tight structure.

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

Completeness5/5

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

For a seven-parameter, open-world write tool with an output schema, the description covers everything an agent needs: trigger, consent flow, dry-run semantics, field constraints, redaction rules, and retry/idempotency behavior. Return values need not be explained since an output schema exists, and the preview behavior is still described where it matters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden, and it does: summary (one line, under 200 chars), details (optional, user's own words, combined under 4000 chars), kind (bug/idea/complaint), tool and error_code (plain lowercase identifiers, otherwise omitted), confirm (default false), and operation_id. Every one of the seven parameters gets meaning the bare schema lacks.

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?

States a specific verb and resource ("Send a bug report, an idea or a complaint to the Meshive team") and anchors it to a known surface ("as the console's Send feedback does"). It is clearly distinguishable from siblings like operation_status or send_host_message, which are unrelated to reporting problems with Meshive itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit trigger conditions (a tool failed with code server_error or a non-JSON error, or the user says something is broken/confusing/missing) and explicit exclusions (errors whose next_step already explains them: rate limits, credit, wrong id, refused request). It also states the consent protocol — ask once per conversation, send only on yes — which is the key decision rule an agent needs.

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