Skip to main content
Glama
Sign In
Backforms MCP

Backforms MCP

by Arneld18
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_forms

Retrieve all form endpoints in a Backforms workspace, including IDs, action URLs, and security settings. Use limit and offset to paginate results.

Instructions

Lists all form endpoints in the Backforms workspace, including their IDs, action URLs, and security configuration.

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
limitNoNumber of forms to retrieve (default: 20, max: 100)
offsetNoPagination offset (default: 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It usefully enumerates the returned payload (including security configuration, which signals sensitive data), but never states that the operation is read-only, how pagination behaves, or what an empty workspace returns.

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 the operation and scope front-loaded and the return inventory following. No filler or repetition.

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 compensates by describing the return contents, and the schema covers both parameters. Missing only pagination behavior and any read-only/safety note, which is minor for a simple enumeration tool.

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 100%, with limit and offset documented including defaults and max. The description adds no parameter detail, so the baseline 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?

States a specific verb (Lists) and resource (form endpoints) with workspace scope, and names the returned fields (IDs, action URLs, security configuration). It does not explicitly contrast with the single-form sibling get_form_details, so sibling differentiation is only implicit.

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 statement and no mention of alternatives, despite siblings like get_form_details covering a single form. The agent must infer that this is the bulk-enumeration entry point rather than a targeted lookup.

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