Skip to main content
Glama

Hilfe durchsuchen

hilfe
Read-only

Antworten aus der Hilfe von MADLAB // Publishing: Domains verbinden und kaufen, DNS und Nameserver, Transfercode, Veroeffentlichen, Versionen, Plaene, Dateien hochladen, Fehlersuche. Bei JEDER Frage zum Portal oder zum Dienst zuerst hier nachsehen statt aus dem Gedaechtnis zu antworten. Findet sich nichts, sagt das Werkzeug es – dann nicht raten, sondern auf den Support verweisen.

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": {
      "frage": "<frage>"
    },
    "name": "hilfe"
  }
}

Input Schema

NameRequiredDescriptionDefault
frageYesDie Frage des Kunden, in seinen Worten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real behavioral information beyond that: the tool reports explicitly when no answer exists, which is unusual and important for the agent's decision loop. It stops short of describing result shape or how many sources are returned, but with no output schema that is a modest gap rather than a serious one.

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 topic list is front-loaded so the agent can match a question domain quickly, followed by the routing rule and the failure fallback. The enumeration is long but each term earns its place as a retrieval cue; there is 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?

For a one-parameter, read-only lookup with no output schema, the definition covers purpose, coverage scope, usage priority and the empty-result path. What is missing is minor: nothing about answer format or whether results cite sources, which an agent might want when relaying an answer to a customer.

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 coverage is 100% and the single parameter is already documented as the customer's question in their own words. The description reinforces that framing ('Bei JEDER Frage') but adds no syntax, phrasing or scope constraints beyond what the schema states. 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?

States a specific resource (answers from the MADLAB help corpus) and enumerates the concrete topic areas it covers: domains, DNS/nameservers, transfer code, publishing, versions, plans, uploads, troubleshooting. An agent can tell this is a documentation-lookup tool and not, say, a live-site diagnostic like check_site or a ticket tool like support_anfrage.

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?

Explicit routing rule: for EVERY portal or service question, consult this tool first instead of answering from memory. It also defines the fallback path — if nothing is found, do not guess, direct the user to support — which is exactly the when/when-not guidance an agent needs.

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