Skip to main content
Glama

Logisticoo Signature

Leistungsprofil / Service profile

get_service_profile
Read-only

Returns what Logisticoo Signature (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.8/5.0
Behavior3/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 by structured data. The description's real contribution is the content inventory (including the unusual "what is not offered" and "whether prices are available" signals), but it says nothing about response shape, size or rate/permission behavior, and there is no output schema to fall back on.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One dense content sentence followed by a short imperative, with the scope stated up front and zero filler. Every clause names distinct content the caller will receive.

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 parameterless read tool with no output schema, listing the returned content sections is largely sufficient. The gap is default-language behavior, which an agent needs to call it predictably.

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?

Schema description coverage is 0%, so the single optional language parameter is undocumented in the schema. The description entirely ignores it, leaving the agent to infer that de/en selects the response language and what the default is; only the self-explanatory enum values make it usable.

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?

Specific verb ("Returns") plus a precisely enumerated resource: services, what is not offered, price availability, inquiry submission, contact and legal links. The enumerated content makes the tool's scope unmistakable and clearly distinct from the write-path siblings preview_inquiry/submit_inquiry, though it never names them.

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 an explicit ordering directive that tells an agent to establish context before the inquiry tools. It stops short of naming alternatives or stating when not to call it, so there is no exclusion 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