Skip to main content
Glama
Sign In

Cactal

by ai.cactal
OverviewDiscussionsAdmin

Mark a submission as spam or not spam

websiteForms_submissions_setStatus
Idempotent

Moves a submission between the inbox and the spam folder. Restoring to inbox sends the notification email if it was never sent. Spam is deleted automatically after 30 days.

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": {
      "websiteId": "<websiteId>",
      "submissionId": "<submissionId>",
      "status": "<status>"
    },
    "name": "websiteForms_submissions_setStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusYes`spam` hides the submission in the spam folder; `inbox` restores it and sends any missed notification.
websiteIdYes
submissionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Adds real context beyond annotations: restoring to inbox sends the missed notification email, and spam is auto-deleted after 30 days. Annotations already cover idempotency and non-destructiveness; the description complements them with side effects and lifecycle. It does not mention permission requirements.

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 short sentences, each carrying a distinct fact (state change, email side effect, retention policy). Front-loaded with the core action and no filler.

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?

No output schema and no annotations gap of consequence; the description covers the meaningful outcomes an agent needs. Missing only auth/permission expectations and whether restoring a pre-30-day spam item is guaranteed, which are minor for this simple toggle.

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 coverage is 33%, but the two undocumented parameters (websiteId, submissionId) are self-evident identifiers. The status enum carries its own description in the schema, which the tool description echoes rather than extends, so it adds little parameter-level meaning.

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?

States a specific state change ('moves a submission between the inbox and the spam folder'), which is a clear verb+resource pairing. It implicitly differentiates from websiteForms_submissions_delete by framing this as reversible folder movement, though it never names that sibling.

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?

Usage is implied by the described effect rather than stated as guidance. It never says when to prefer this over websiteForms_submissions_delete or how to locate a submission (list/get), so the agent must infer the workflow.

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