Skip to main content
Glama

Formular anschliessen

formular_einbauen
Read-only

Sagt, wie ein Formular dieser Website an unseren Formular-Dienst angeschlossen wird: Adresse (action="/__formular", method="post"), Steuerfelder, Spamschutz und der Absatz für die Datenschutzerklärung. Nur auf unserem Hosting (Free und MADLAB-Hosting); beim Plan «eigenes Hosting» läuft ein Formular über das Hosting des Kunden. Einträge kommen ins Portal (Reiter «Formulare») und als Mail an die Adresse, die der Kunde dort hinterlegt (sonst an die Inhaber des Kontos) – nie an eine Adresse aus dem Formular. Schreibt nichts; das Formular baust du mit fs_write.

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": {
      "website": "<website>"
    },
    "name": "formular_einbauen"
  }
}

Input Schema

NameRequiredDescriptionDefault
spracheNoSprache der WEBSITE, für den Datenschutz-Absatz und die Antwortseiten. Vorgabe: de.
websiteYesKennung oder Name der Website. Reicht der Zugang ueber mehrere Organisationen und gibt es die Kennung mehrfach, «organisation/website» schreiben.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the readOnlyHint=true and destructiveHint=false annotations, it discloses that nothing is written, where submissions land (portal tab «Formulare» plus mail to the address stored by the customer, falling back to account owners, never to a form-supplied address), and the hosting-plan gate. It does not describe the shape of what it returns (presumably an instruction text), which is the only behavioral gap.

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?

Four sentences, each carrying distinct information: the wiring address/fields, the hosting restriction, the delivery path for submissions, and the explicit no-write/fs_write handoff. Front-loaded with the technical core, no filler or repetition.

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 read-only guidance tool with two parameters and no output schema, the description covers everything an agent needs: applicability by hosting plan, what gets generated, where entries end up, and which sibling performs the write. Nothing required for correct invocation is missing.

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%, so both parameters are already documented, including the language enum and the «organisation/website» disambiguation for ambiguous identifiers. The description only echoes the privacy-paragraph relevance of the language, adding no syntax or format detail beyond the schema; baseline 3 applies.

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?

The description states a specific function: it explains how a form on this website is wired to the provider's form service (action="/__formular", method="post", control fields, spam protection, privacy paragraph). It also names the sibling it is not – "Schreibt nichts; das Formular baust du mit fs_write" – so an agent can distinguish it from the file-writing tool without opening either schema.

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?

Both when-to-use and when-not-to-use are explicit: it applies only on their hosting (Free and MADLAB), while the «eigenes Hosting» plan routes forms through the customer's hosting. The alternative for the actual build step (fs_write) is named directly, leaving nothing to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources