Skip to main content
Glama

leistungen

List the services offered by the business to answer customer questions about available offerings. Use it to retrieve service information quickly.

Instructions

List the services of the business. Auskunft über die Leistungen des Betriebs.

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": "leistungen"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.2

TDQS

B3/5.0
Behavior2/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 of describing behavior. "List" implies a read-only operation, but the description says nothing about the return format, pagination, filtering, or whether all services are returned. For a no-parameter listing tool, the burden is light, but the description still adds almost no behavioral detail.

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 description is short and front-loaded with the English statement of purpose, which is good. The second sentence is a German translation of the first and adds no new information, so it is pure repetition. The description would be tighter as a single 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?

This is a simple, zero-parameter listing tool with no output schema, so the description does not need to explain much. It states what the tool lists but not what each service record contains or how results are ordered or paginated. It is adequate but not complete.

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 no parameters, so the schema needs no explanation and the baseline score is 4. The description correctly implies that the tool takes no input and simply returns the business's services, and it introduces no parameter semantics that would be misleading.

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 description gives a specific verb and resource: "List the services of the business." That is enough for an agent to know what the tool returns. It does not mention the sibling tool anfrage_anlegen, but that sibling is a write operation for inquiries and is unlikely to be confused with listing services, so the gap is minor.

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?

The description gives no guidance on when to use this tool versus alternatives, and it lists no prerequisites or exclusions. An agent can infer that it should be called when service information is needed, but nothing in the text states that, and it does not name anfrage_anlegen or any other route.

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