Skip to main content
Glama
ignsm

formhaus-mcp

by ignsm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Formhaus capabilities

capabilities
Read-only

Get the full Formhaus definition reference before writing or editing forms: field types, props, validation, conditions, steps, actions, translations, and adapters.

Instructions

Call this first, before writing or editing a definition, for the full reference of what a definition supports; example_definitions gives whole working forms to copy instead. Lists what a Formhaus definition supports: field types, sections, repeatable groups, field props, validation rules, condition operators, step and route semantics, actions, translation (lang, messages, labels, i18n keys, overlay addresses) and adapters. To check a finished definition, call validate_definition instead. To upgrade a 0.10 project, read the formhaus://migrate/0.11 resource.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
i18nNo
stepsYes
groupsYes
actionsYes
adaptersYes
sectionsYes
conditionsYes
definitionYes
fieldPropsYes
fieldTypesYes
containerTypesYes
fieldTypeNotesYes
validationRulesYes
customFieldTypesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.13.3
    • addedOutput schema / properties / containerTypes
      Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / fieldTypeNotes
      Added value: +{
+  "additionalProperties": {
+    "type": "string"
+  },
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / groups
      Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • addedOutput schema / properties / sections
      Added value: +{
+  "additionalProperties": {},
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • changedOutput schema / required
      Previous value: -[
-  "definition",
-  "fieldTypes",
-  "customFieldTypes",
-  "fieldProps",
-  "validationRules",
-  "conditions",
-  "steps",
-  "actions",
-  "adapters"
-]New value: +[
+  "definition",
+  "fieldTypes",
+  "customFieldTypes",
+  "containerTypes",
+  "sections",
+  "groups",
+  "fieldTypeNotes",
+  "fieldProps",
+  "validationRules",
+  "conditions",
+  "steps",
+  "actions",
+  "adapters"
+]
  2. First observedv0.13.1

TDQS

A4.6/5.0
Behavior4/5

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

The readOnlyHint annotation already establishes that this is a safe, non-mutating lookup. The description adds genuine context beyond that: it is a full capability reference intended to be consulted before authoring, with an output schema available for return-value details. It does not discuss any limits or caching, but for a no-arg read-only reference tool little more is needed.

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?

Roughly three sentences, each doing distinct work: the call-first directive with alternatives, the coverage list, and the routing notes. The enumeration of coverage areas is long but earns its place by telling the agent whether this reference answers its question. Slightly list-heavy rather than wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read-only reference tool with an output schema, the description covers purpose, timing, sibling alternatives, and a migration resource pointer. Nothing an agent needs in order to call it correctly is missing.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is no parameter surface for the description to clarify or omit.

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 and resource ('Lists what a Formhaus definition supports') and enumerates the coverage areas, so the agent knows exactly what reference material it returns. It also explicitly names what it is not: 'example_definitions gives whole working forms to copy instead' and 'call validate_definition instead'.

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?

Gives an explicit trigger ('Call this first, before writing or editing a definition'), a stated alternative for a different need (example_definitions for copyable forms), a different alternative for checking results (validate_definition), and a resource pointer for migration. Nothing about when or when-not is left 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