Skip to main content
Glama

Logisticoo Freight

Leistungsprofil / Service profile

get_service_profile
Read-only

Returns what this road freight forwarder offers: services, served countries, vehicle classes with capacities, how indicative prices are calculated, what needs a manual quote, how to submit an inquiry, contact and legal links. Call this first. DE: Leistungen, Länder, Fahrzeugklassen, Preisregeln, Anfrageweg, Kontakt.

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 real value by disclosing the breadth of returned content, including that some needs require a manual quote — context an agent cannot get from the annotations alone. It says nothing about caching, rate limits or response size, which keeps it from a 5.

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?

The English sentence is front-loaded with the scope and ends with the actionable 'Call this first'. The trailing German sentence largely duplicates the same list, which is defensible for a bilingual audience but is still repeated content.

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 no output schema, the description carries the burden of explaining returns, and it does so by enumerating the profile sections. The only material omission is any explanation of the language parameter, so it is nearly but not fully complete.

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 tool has one parameter, language (enum de/en), and schema description coverage is 0%. The description never mentions the language parameter at all; only the enum values in the schema make its meaning inferable, so the description fails 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?

States a specific verb and resource (returns the forwarder's service profile) and enumerates exactly what it covers: services, countries, vehicle classes with capacities, price rules, manual-quote needs, inquiry path, contact and legal links. It also instructs 'Call this first', which clearly separates it 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 clear sequencing rule relative to estimate_transport_price, preview_inquiry and submit_inquiry. It does not state when not to use it or name alternatives explicitly, so it falls short of the top band.

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