firma.de Rechner für Gründer

Gründung-starten-API von firma.de

gruendung_starten

Read-onlyIdempotent

Macht aus einer Geschäftsidee den Link, der den Gründungs-Chat von firma.de mit dieser Idee öffnet (UG, GmbH, GbR, Einzelunternehmen und mehr). Liefert nur den Link: es wird nichts angelegt, bis die Person ihn öffnet. Offen, ohne Schlüssel, speichert nichts.

Link in den Gründungs-Chat von firma.de aus einer Geschäftsidee.

Antwortet auf Deutsch, als Text oder JSON. Der Rechner für Menschen: https://www.firma.de/

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "Köln",
      "idea": "Café mit Röstzeit und Frühstück im Belgischen Viertel",
      "founders": 2,
      "legalForm": "ug",
      "startMonth": "2027-03"
    },
    "name": "gruendung_starten"
  }
}

Input Schema

Name	Required	Description	Default
`city`	No	Ort oder Stadt, falls schon klar.
`idea`	Yes	Die Geschäftsidee in eigenen Worten (10 bis 1000 Zeichen): was das Unternehmen macht, für wen.
`format`	No	md (Standard): die Antwort als lesbarer Text mit Link in den Rechner, kurz genug für den Chat. json: alle Werte als JSON.	md
`locale`	No	Sprache des Gründungs-Chats: de (Standard) oder en.
`founders`	No	Anzahl der Gründer.
`legalForm`	No	Rechtsform, falls schon klar.
`startMonth`	No	Geplanter Start als YYYY-MM.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false. The description adds genuinely non-structured context: it only returns a link, nothing is created until the person opens it, and it needs no key and stores nothing. It does not describe the response payload shape beyond 'Text oder JSON', which keeps it from a 5.

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?

The opening paragraph is front-loaded and efficient, with the key constraint ('Liefert nur den Link') in the second sentence. However, the follow-up paragraph repeats the purpose nearly verbatim ('Link in den Gründungs-Chat von firma.de aus einer Geschäftsidee'), which is redundant rather than additive.

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 link builder with 7 fully documented parameters and a single required field, the definition covers what the tool is, what it returns, and that it causes no side effects. The main omission is guidance on choosing this tool over the sibling costing/budget calculators, which the description never addresses.

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% and every parameter (idea, city, founders, legalForm, startMonth, format, locale) is documented in the schema itself. The description only echoes the legal-form options (UG, GmbH, GbR, Einzelunternehmen), adding little beyond what the enum already provides, so 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?

The first sentence gives a concrete verb and output ('Macht aus einer Geschäftsidee den Link, der den Gründungs-Chat ... öffnet') and names the legal forms it covers, so the resource and result are unambiguous. It never names or distinguishes itself from sibling calculators like gruendungskosten or gruendungsbudget, so it falls short of the sibling-differentiation bar for a 5.

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?

Usage is only implied: an agent can infer the tool applies when someone has a business idea and wants to enter the firma.de founding chat. There is no explicit when-to-use, when-not-to-use, or pointer to an alternative among the many calculator siblings.

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

All firma.de Rechner für Gründer tools Inspect

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

Need Help?