Skip to main content
Glama

co.build

Prepare feedback for a mod's maintainer

prepare_feedback

After the owner has actually used a mod and agreed to leave feedback, prepare a private preview of a public post on its cobuild page. kind: comment (praise, a bug, friction), feature_request (something it can't do yet), reply (to parentId, any entry on this mod), or support (upvote the feature request parentId, with the owner's note as an optional reply). text is the owner's own words, quoted or lightly tidied; never invent or add opinions. Add only context you confirmed: tried, expected, actual, modelId, firmware, modVersion, platform. Before a feature request, read get_feedback with featureRequests: true; if one asks for the same thing, use support instead. Never include personal data, logs, health readings or secret values. Returns the exact action and public text. Show both with the public account attribution and ask explicit approval before publish_feedback. Expires after 30 minutes. This does not publish.

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": {
      "modId": "<modId>",
      "kind": "<kind>"
    },
    "name": "prepare_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
textNoThe owner's own words, quoted or lightly tidied; never add opinions. Required except for support.
modIdYesMod slug or mod: search ID.
triedNoWhat the owner tried, if they said.
actualNoWhat happened instead.
modelIdNoExact hardware model ID from get_device, only if confirmed.
deviceIdNoThe device it was used with, if not the mod's own: a slug or device: ID.
expectedNoWhat they expected to happen.
firmwareNoDevice firmware, only if confirmed.
parentIdNoFor reply or support: the entry id from get_feedback (for support, a featureRequest entry).
platformNo
modVersionNoThe mod's version, only if confirmed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare the mutation/safety profile; the description adds substantial context beyond them: the preview expires after 30 minutes, it does not publish, it returns the exact action and public text, and explicit approval must be obtained before publish_feedback. It also states privacy constraints (no personal data, logs, health readings, secret values) and a no-invention rule for text.

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?

Dense but front-loaded: the core action and the 'does not publish' boundary come first, followed by kind rules, sourcing constraints, and the approval/expiry mechanics. A single long paragraph rather than structured lines costs it a point, but nearly every sentence carries operational information.

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 12-parameter mutation tool with no output schema, the description covers the return value ('the exact action and public text'), the lifecycle (30-minute expiry), the required follow-up (explicit approval, then publish_feedback), and the data-handling limits. Nothing an agent needs to call it correctly is missing.

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 83%, so the baseline is 3, but the description adds real meaning: it defines each kind value (praise/bug/friction, something it can't do yet, reply to parentId, upvote of a feature request), clarifies that parentId for support must be a featureRequest entry, and constrains text to the owner's own words. It does not explain the confirmed-context fields (tried/expected/actual/firmware) beyond listing them, which the schema already covers.

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: 'prepare a private preview of a public post on its cobuild page', and explicitly disambiguates from the publishing sibling with 'This does not publish.' An agent can distinguish it from publish_feedback without opening either schema.

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 an explicit precondition ('After the owner has actually used a mod and agreed to leave feedback'), a decision rule for choosing among the four kinds, and a named alternative path: read get_feedback with featureRequests: true first and use support if a duplicate exists. When-to-use and when-to-use-something-else are both covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources