Skip to main content
Glama
Sign In

Cactal

by ai.cactal
OverviewDiscussionsAdmin

Submit product feedback

feedback_submit

Adds user-requested free-form feedback to the Cactal product-feedback inbox. Describe what happened and what would have made the experience better. Agents must set authorKind to agent even when acting through a user OAuth connection. Never include credentials, secrets, raw sensitive user content, or unnecessary personal or customer data.

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": {
      "authorKind": "<authorKind>",
      "feedback": "<feedback>"
    },
    "name": "feedback_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
feedbackYesConcise free-form feedback describing the Cactal problem or limitation and what would have made the experience better.
authorKindYesWho wrote the feedback. An AI agent must pass "agent" even when connected through a user OAuth token.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare the mutation/safety profile (readOnly=false, destructive=false, non-idempotent). The description adds concrete context beyond that: the submission lands in a human-reviewed feedback inbox and must not contain credentials, secrets, or unnecessary personal data – a genuinely useful disclosure for a write tool.

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

Conciseness5/5

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

Three sentences: purpose, content guidance, hard constraint. Front-loaded with the action and nothing repetitive – every sentence carries distinct instruction.

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 two-parameter append-only tool with full schema coverage and no output schema, the description covers what it does, how to word the input, and the critical authorKind rule. 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 100%, so the baseline is 3, but the description reinforces the non-obvious half of the authorKind semantics ('must set authorKind to agent even when acting through a user OAuth connection'), which is the most error-prone decision an agent makes here. It also restates the feedback content expectation in plain language.

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 ('Adds') and resource ('user-requested free-form feedback to the Cactal product-feedback inbox'), naming the destination explicitly. No sibling is a feedback tool, so it is trivially disambiguated from the CMS/website/docs tools around it.

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?

Gives clear guidance on what to put in the feedback ('describe what happened and what would have made the experience better') and frames it as user-requested, so the agent knows the context that warrants calling it. No explicit when-not or alternative is stated, and none exists among siblings, so a 4 rather than a 5.

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

All Cactal toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources