Skip to main content
Glama

Wrenform Quick Forms

Check a quick form

check_quick_form
Read-onlyIdempotent

Check whether a quick form has been confirmed: pending_confirmation, active, expired or declined. No submission data is available here; to manage the form, the user signs in at https://wrenform.com/app.

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

Input Schema

NameRequiredDescriptionDefault
form_idYesThe form's ID, as returned by list_forms or create_form (12 letters and digits).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value beyond that by disclosing the possible return states and explicitly stating it exposes no submission data, which matters since there is no output schema.

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?

Two short sentences with zero filler: the first states what is returned, the second bounds what is not offered and where to go instead. The essential information is front-loaded.

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 single-parameter read tool with full annotations but no output schema, the description covers the result states and the data boundary, which is what the agent needs. It omits error/not-found behavior, but that is a minor gap rather than a blocker.

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?

There is only one parameter and schema coverage is 100% — the schema already explains form_id's format (12 letters and digits) and its provenance from list_forms or create_form. The description adds no additional meaning about the parameter, so the baseline of 3 applies.

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?

Uses a specific verb ('Check') on a specific resource ('quick form') and enumerates the exact outcome states (pending_confirmation, active, expired, declined), so the agent knows precisely what question this tool answers. It does not explicitly contrast with siblings like create_quick_form, but the resource names are distinct enough that confusion is unlikely.

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?

Provides clear negative scoping: no submission data is available here, and management happens in the web app at the given URL. That tells the agent when not to use it, though it gives no explicit trigger condition (e.g. 'call after create_quick_form to poll for confirmation') and names no in-catalog alternative.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources