Skip to main content
Glama

Notfall-Spedition

Leistungsprofil / Service profile

get_service_profile
Read-only

Returns what Notfall-Spedition (Logisticoo GmbH) offers: services, what is not offered, whether prices are available, how to submit an inquiry, contact and legal links. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
languageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description's job is to add content-level behavior — and it does: it discloses that the response includes what is NOT offered and whether prices are available, which prevents the agent from assuming pricing data will be present. it does not say whether the content is static or how the language affects the payload, so a small gap remains.

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?

One front-loaded sentence with a colon-delimited content list, followed by a short imperative. Every clause maps to real information; the enumeration is dense but no sentence is wasted. It could be tightened slightly, but there is no filler.

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 zero-required-parameter, read-only entry-point tool with no output schema, this covers what an agent needs: what comes back and that it should be called before other steps. Only the language parameter's default behavior is left unaddressed, which is minor at this complexity.

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?

The single parameter (language, enum de/en) has 0% schema description coverage and is never mentioned in the description. The enum values are self-explanatory, which keeps this from being a serious gap, but the description does not state the default language or what happens when the parameter is omitted.

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?

States a specific verb (returns) and a concrete resource (the service profile for Notfall-Spedition/Logisticoo GmbH), then enumerates the content classes: services, non-offered services, price availability, inquiry process, contact and legal links. That breadth makes the tool's identity unambiguous. It stops short of naming the siblings (preview_inquiry, submit_inquiry), so differentiation is only implicit via 'how to submit an inquiry'.

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

Usage Guidelines4/5

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

'Call this first' gives a clear sequencing directive that tells the agent when to reach for this tool relative to other steps. There is no explicit when-not or named alternative, so it sits at clear-context-without-exclusions rather than full routing guidance.

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