Skip to main content
Glama
Sign In

BootForm

by com.bootform
OverviewDiscussionsAdmin

Mark a submission

bootform_mark_submission
Idempotent

Marks one submission (one submission_id per call; call it once per submission for several) read/unread, starred/unstarred, archived/unarchived, and/or moves it to the spam folder (spam: true) or back to the inbox (spam: false). Moving only changes the folder: no notification is sent late and the quota does not change. Name the submission and ask the person before moving it. At least one of read/starred/archived/spam is required. To show or hide a submission in the form's public content feed use bootform_moderate_submission; to delete submissions permanently use bootform_delete_submissions.

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": {
      "form_id": "<form_id>",
      "submission_id": "<submission_id>"
    },
    "name": "bootform_mark_submission"
  }
}

Input Schema

NameRequiredDescriptionDefault
readNoTrue to mark read, false to mark unread. Omit to leave unchanged.
spamNoTrue moves it to the spam folder, false moves it back to the inbox ("not spam"). Omit to leave unchanged.
form_idYesThe form's id
starredNoTrue to star, false to unstar. Omit to leave unchanged.
archivedNoTrue to archive, false to unarchive. Omit to leave unchanged.
submission_idYesThe submission's id

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?

Goes well beyond the annotations: discloses that a folder move sends no notification and does not change quota, and imposes a human-confirmation step before moving. Annotations already cover safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false), so the remaining gap is minor — no mention of permission requirements or what happens on partial failure.

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?

Front-loaded with the core action and its state axes, then constraints, then sibling routing. Dense but nearly every clause carries a distinct constraint; the phrasing around 'no notification is sent late' is slightly awkward and costs a little polish.

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?

For a six-parameter mutation tool with full schema coverage and no output schema, the description covers call shape, preconditions, side effects, confirmation policy, and sibling routing. Only the return shape (what the updated submission looks like) is left implicit, which is a small omission.

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 baseline is 3; the description adds value by spelling out that spam:true means move to spam and spam:false means move back to inbox, and by imposing the at-least-one-flag rule that the schema itself does not encode (only form_id and submission_id are required).

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 (marks) on a specific resource (one submission) and enumerates the exact state axes it toggles: read, starred, archived, spam. It also names the two siblings that do adjacent things (bootform_moderate_submission, bootform_delete_submissions), so an agent can route without opening another 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?

Explicit call-shape guidance ('one submission_id per call; call it once per submission for several'), an explicit precondition ('At least one of read/starred/archived/spam is required'), an explicit confirmation rule ('ask the person before moving it'), and explicit alternatives for the neighboring operations.

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

All BootForm 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