Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Get form

get_form
Read-only

Retrieve one form's full details—fields, settings, and submission count—by id or slug. Use it after listing forms to inspect the structure and settings needed for processing submissions.

Instructions

Get one form's full details (fields, settings, submission count) by id or slug.

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": {
      "idOrSlug": "<idOrSlug>"
    },
    "name": "get_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
idOrSlugYesThe form's id or slug (from list_forms)

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: +[
      +  "idOrSlug"
      +]
  2. First observedv0.73.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine value by naming the returned payload contents (fields, settings, submission count), but says nothing about error behavior for a missing form or whether the response is large/heavy.

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?

One compact sentence with the resource and return contents front-loaded and no filler. The parenthetical is efficient, though it slightly clutters reading flow.

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 telling the agent what comes back, and it names the three main payload areas. For a single-parameter read tool with readOnly annotations, this is nearly complete; only error/not-found handling is unaddressed.

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% and the single parameter already documents that it accepts an id or slug sourced from list_forms. The description restates the same dual-key semantics without adding format, validation, or precedence rules (e.g., if a slug collides with an id).

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 and resource ("Get one form's full details") and scopes it to a single record via "one form ... by id or slug", which distinguishes it from list-style siblings. It stops short of naming an alternative tool explicitly, so it is clear but not fully differentiated.

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?

The lookup key ("by id or slug") is stated, implying a direct-fetch use case, and "from list_forms" in the schema points at how ids are discovered. There is no explicit when-to-use versus when-to-use-a-list or search, and no stated behavior when the id is unknown.

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