Skip to main content
Glama
Sign In

123FormBuilder MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Change notification email in 123FormBuilder

123formbuilder_change_notification_email
Read-onlyIdempotent

Change notification email in the user's own 123FormBuilder account from ChatGPT, Claude or any AI agent. Returns how to do it in 123FormBuilder step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's 123FormBuilder Cloud Browser. 123FormBuilder's official API: 123FormBuilder has a REST API v2 with token login (checked 23 Oct 2026).

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": "123formbuilder_change_notification_email"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

readOnlyHint=true is consistent with 'opens nothing by itself', and the description adds real context beyond the annotations: the return is a screen/button/field walkthrough, not an action. It stops short of describing the response shape or length, but the key behavioral contract (no side effects, instructional output) is disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core two clauses are front-loaded and useful, but 'from ChatGPT, Claude or any AI agent' is filler, and the trailing sentence about 123FormBuilder's REST API v2 with token login and a 'checked 23 Oct 2026' date adds nothing an agent needs to invoke this tool.

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 no-parameter, read-only guidance tool with no output schema, the description covers enough: what it returns (step-by-step screens/buttons/fields) and that it performs no action. The API tangent is noise rather than a gap that would cause a mis-call.

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 there is nothing for the description to disambiguate; the empty schema and the description agree. Baseline for a no-parameter tool.

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 resource (notification email in the user's 123FormBuilder account) and, crucially, clarifies that the tool only returns step-by-step instructions rather than performing the change. It explicitly separates itself from the cotlet_browser_* tools, so an agent can pick correctly without opening any schema.

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?

Tells the agent exactly what to do next: this tool yields the procedure, then the actual change is done via cotlet_browser_* tools in the user's Cloud Browser. There is no explicit 'when not to use' or mention of a direct-API alternative, but the follow-on path is unambiguous.

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

All 123FormBuilder MCP Server and API by Cotlet toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources