Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Update form submission status

update_form_submission_status
Destructive

Change a form submission's status to pending, processed, spam, or archived. Use it to triage, approve, or flag incoming submissions by ID.

Instructions

Update a form submission's status (pending, processed, spam, archived).

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

Input Schema

NameRequiredDescriptionDefault
statusYesNew status
submissionIdYesThe submission's id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / required
      Added value: +[
      +  "submissionId",
      +  "status"
      +]
  2. First observedv0.73.1

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is known from structured data. The description adds nothing beyond that: it does not say whether the prior status is lost, whether changing status to 'spam' or 'archived' triggers notifications, webhooks, or filtering side effects, or whether the change is reversible — meaningful gaps for a destructive mutation.

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?

A single sentence with zero wasted words, with the resource and the allowed values front-loaded. For a two-parameter tool this is appropriately sized.

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

Completeness3/5

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

For a simple two-parameter tool with full schema coverage and no output schema, the essentials are present. However, as a flagged destructive mutation it should explain side effects of a status change or what is returned, which the definition omits.

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 100%, with both submissionId and status fully documented and the status enum declared in the schema. The description merely repeats the enum values the schema already lists, adding no extra meaning such as valid transitions or constraints.

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 verb ('Update') and resource ('form submission's status') and enumerates the exact status values, so the scope is unambiguous. It is implicitly distinct from siblings like get_form_submission or delete_form_submission, but it does not explicitly name how it differs from them.

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?

There is no when-to-use guidance, no mention of prerequisites or required permissions, and no reference to alternatives. An agent must infer that this is the tool for changing an existing submission's state rather than creating or deleting one.

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

Deploy Server

Other Tools