Skip to main content
Glama

Speed Logistics

Leistungsprofil / Service profile

get_service_profile
Read-only

Returns what Speed Logistics (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 description's job is to add content knowledge — and it does, notably that the response includes negative space ("what is not offered") and price availability, which shapes how an agent should reason. It says nothing about response shape or size, but for a static read-only profile tool that is a minor gap.

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 dense sentence with zero filler, and the resource is front-loaded. The most actionable clause ("Call this first") is buried at the end rather than leading, which costs a point on structure.

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?

With a single optional parameter and no output schema, an agent has what it needs: what the tool returns, why to call it, and when. The only real omission is any statement about the `language` parameter's behavior.

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) is never mentioned in the description, and schema description coverage is 0%, so nothing explains what it controls, whether there is a default, or what happens if omitted. The self-explanatory enum values keep this from a 1, but the description does not 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?

States a specific verb and resource ("Returns what Speed Logistics ... offers") and then enumerates exactly what the payload covers: services, what is *not* offered, price availability, inquiry submission, contact and legal links. An agent can tell this apart from the inquiry siblings (preview_inquiry, submit_inquiry) without opening any schema.

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 explicit ordering guidance relative to the inquiry tools, which is the key usage decision here. There are no when-not-to-use exclusions or stated prerequisites, so it stops short of a 5.

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