Skip to main content
Glama
Sign In
agent-card-starter

agent-card-starter

by flowboxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

anfrage_anlegen

Creates a non-persistent inquiry stub for a service, capturing a message and preferred contact method without storing data.

Instructions

Create an inquiry (stub, nothing is stored). Anfrage anlegen (Stub, nichts wird gespeichert).

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": {
      "leistung": "<leistung>",
      "nachricht": "<nachricht>",
      "rueckmeldung": "<rueckmeldung>"
    },
    "name": "anfrage_anlegen"
  }
}

Input Schema

NameRequiredDescriptionDefault
leistungYesid from the tool 'leistungen'
nachrichtYes
rueckmeldungYeshow the business may answer (e-mail or phone)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

C2.9/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does disclose the single most important behavioral trait — the call is a stub and persists nothing — but says nothing about permissions, what the stub returns, or whether the inquiry is transmitted anywhere.

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 definition is short but half of it is a verbatim German translation of the German tool name, which restates rather than adds. The informative caveat ('nothing is stored') is buried in a parenthetical and then repeated in the mirrored German sentence.

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

Completeness3/5

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

For a three-required-parameter stub with no output schema and no annotations, the description covers the crucial no-op behavior but omits what a caller gets back and how the parameters relate to the sibling tool. An agent could invoke it, but would be guessing about the leistung reference and the response shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, and the description adds no parameter meaning whatsoever. It does not explain that leistung is an id sourced from the 'leistungen' tool, what nachricht should contain, or the 1000-character limit; all of that lives only in the schema. For a tool where one parameter is a cross-tool reference, the description should have reinforced it.

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 English clause names a specific verb and resource ('Create an inquiry') and adds a material qualifier ('stub, nothing is stored'). This is clear enough for an agent to know what the tool does, though it does not differentiate itself from the sibling 'leistungen' beyond the indirection embedded in the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool, when not to, or how it relates to 'leistungen' (which supplies the required leistung id). The only contextual signal is the 'nothing is stored' caveat, which hints at a dry-run/preview semantics but never states that explicitly.

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