Skip to main content
Glama

Spedition Log

Leistungsprofil / Service profile

get_service_profile
Read-only

Returns what Spedition Log (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

A4/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 remaining burden is content disclosure, and the description does that well by telling the agent it will learn what is *not* offered and whether prices are available. It does not describe response shape or size, but with no output schema the content enumeration largely carries that load.

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?

A single dense sentence enumerating payload contents followed by a short imperative ("Call this first") — front-loaded and free of filler. The enumeration is list-like and slightly crammed, but each item conveys distinct information.

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 discovery tool with no output schema and a single optional enum parameter, the description covers purpose, contents and call ordering adequately. The only real omission is any explanation of the `language` parameter's effect and default.

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?

The single `language` parameter (enum de/en) has 0% schema description coverage and is never mentioned in the description, so the agent is not told what it controls or what the default is. The enum values are self-evident enough to avoid a 1, but the description does nothing to compensate for the coverage gap.

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?

Uses a specific verb ("Returns") with a named resource (the service profile of Spedition Log / Logisticoo GmbH) and enumerates the payload: services, what is not offered, price availability, inquiry submission, contact and legal links. That enumeration makes it clearly distinct from the pricing and inquiry siblings.

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 concrete ordering directive relative to the other tools, which is exactly what an agent needs as an entry point. It stops short of stating when this tool is not needed or explicitly naming the alternatives to defer to afterward.

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