Skip to main content
Glama

Logisticoo Tech Logistics

Leistungsprofil / Service profile

get_service_profile
Read-only

Returns what Logisticoo Tech 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 declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds that the return is a fixed informational profile whose scope is enumerated. Because there is no output schema, this enumeration of returned content is the main evidence of what the agent will receive, and it does that job well.

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 packing the six content areas, followed by a front-loaded imperative 'Call this first.' No filler, though the run-on enumeration reads as a list stuffed into prose rather than being formatted for scanning.

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 low-complexity, zero-required-parameter read tool with no output schema, the description covers purpose, content scope and invocation timing adequately. The one material gap is the undocumented language parameter, which an agent must guess at.

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 parameter 'language' has 0% schema description coverage and the description never mentions it. The enum restricts values to de/en, but the agent is not told whether it controls the language of the returned profile, whether it is required, or what the default is when omitted.

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 ('Returns') plus the exact payload: services offered, what is not offered, price availability, inquiry submission path, contact and legal links. The enumeration makes it unmistakable that this is an orientation/profile tool, not the inquiry preview or submit 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 explicit ordering guidance that selects this tool over the siblings at the start of a session. It stops short of naming preview_inquiry or submit_inquiry as follow-on steps or stating when it need not be called again, so it is clear but not a full when/when-not matrix.

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