Cactal

List forms

websiteForms_list

Read-onlyIdempotent

Returns every form with inbox and spam counts, whether the published site still references it, who it notifies, the number of inbox submissions since the caller last opened the Forms tab, and monthly usage against the Free plan limit (limit is null on paid plans). Forms come from <form method="post" action="/_cactal/forms/<name>"> in the website source and appear here as soon as the draft or published build contains them, before any submission.

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>"
    },
    "name": "websiteForms_list"
  }
}

Input Schema

Name	Required	Description	Default
`websiteId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, but the description adds real behavioral context: the unread inbox count is per-caller since they last opened the Forms tab, monthly usage is measured against the Free plan limit (null on paid plans), and forms appear as soon as a build contains them—even before any submission. That goes meaningfully beyond the annotations, though auth requirements and pagination are unaddressed.

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?

The description is front-loaded with the return payload and avoids filler, though it is a single long sentence with many comma-separated clauses. The provenance detail about the <form> tag earns its place by explaining when forms appear.

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?

With no output schema, the description carries the burden of explaining the return values, and it does so thoroughly—counts, references, recipients, unread status, and plan limits. It is nearly complete for a simple one-parameter list tool; only the websiteId meaning and any access requirements are left implicit.

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 0%, so the description should define websiteId, but it never mentions the parameter explicitly. It does reinforce that the operation is scoped to a website and its source code, which makes websiteId's meaning obvious, but it adds little semantic detail beyond the schema.

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 opens with a specific verb and resource: 'Returns every form with inbox and spam counts...' which clearly states what the tool retrieves. The resource 'forms' is inherently distinct from sibling submission tools, but the description never explicitly contrasts itself with websiteForms_submissions_list, keeping it from a 5.

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

Usage Guidelines2/5

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

The description explains what will be returned but gives no guidance on when to call this versus websiteForms_submissions_list or other forms-related tools. There are no prerequisites or exclusions stated, leaving usage to be inferred from the tool name.

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

All Cactal tools Inspect

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

Need Help?