Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

List forms

list_forms
Read-only

Retrieve forms in a Cmssy workspace, filter by draft, published, or archived status, and paginate results using skip and limit parameters.

Instructions

List the forms in the workspace. Filter by status; page on with skip while hasMore is true.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_forms"
  }
}

Input Schema

NameRequiredDescriptionDefault
skipNo
limitNo
statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.146.2
    • changedInput schema / properties / skip / minimum
      Previous value: --9007199254740991New value: +0
  2. Changed3 schema fields changedv0.73.2
    • addedInput schema / additionalProperties
      Added value: +false
    • removedInput schema / properties / limit / default
      Removed value: -50
    • removedInput schema / properties / skip / default
      Removed value: -0
  3. First observedv0.73.1

TDQS

A3.6/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 useful behavioral detail about the pagination contract (skip-based paging driven by a hasMore flag), but omits ordering, default page size, and whether archived forms are excluded by default.

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 compact sentences, purpose first, then mechanics, with zero filler. The terse phrasing of the paging rule still reads unambiguously.

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 simple read-only list tool with annotations covering safety and no output schema to explain, the description covers purpose, filtering, and how to continue paging. The remaining gaps (default limit, sort order, default status inclusion) are minor but real for an agent assembling a paging loop.

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 carries the burden and only partially compensates: it explains status filtering and the role of skip in paging, but never mentions limit or the relationship between skip and limit (page size). Two of three parameters get meaning; one remains undocumented in both schema and description.

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 ("List the forms") plus the scope ("in the workspace"), which is more than a restatement of the title. It does not, however, distinguish itself from the closely named sibling list_form_submissions, so an agent must infer the boundary between forms and form submissions.

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 description gives operational guidance for filtering ("Filter by status") and pagination ("page on with skip while hasMore is true"), which is actionable. It offers no when-to-use/when-not guidance and names no alternative tool, leaving the choice against siblings like list_form_submissions to inference.

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