Skip to main content
Glama

Logisticoo Machinery

Leistungsprofil / Service profile

get_service_profile
Read-only

Returns what Logisticoo Machinery (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?

The annotations already declare readOnlyHint=true and destructiveHint=false, so a safe read is established; the description reinforces this by framing the tool as a static catalogue of offerings, contact and legal links. It says nothing about whether answers are cached, localized, or stable over time. With annotations carrying the safety profile, a 3 is right — some added value, no rich behavioral detail.

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 tightly packed sentence that front-loads the verb and the payload list, closing with the actionable directive. Nothing is redundant and nothing important is buried.

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 one-parameter, read-only profile tool with no output schema, the description covers what an agent needs to decide to call it and what the response will discuss. The only loose end is the language parameter's effect on the response, which neither schema nor description explains.

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?

There is one optional parameter, language, with 0% schema description coverage; the de/en enum is self-explanatory but the description never mentions it or says that output is localized. The description's enumeration of returned content compensates somewhat, but it leaves the single parameter entirely to the schema.

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?

The description uses a specific verb ("Returns") plus an enumerated inventory of the resource: services, non-offered services, price availability, inquiry process, contact and legal links. That is far more concrete than the title alone and clearly marks it as a capabilities/overview tool rather than a transactional one. It stops short of naming the sibling tools (preview_inquiry, submit_inquiry) that a reader might confuse it with, so it is not a clean 5.

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" is an explicit ordering instruction that tells the agent to use this as the entry point before the inquiry siblings. There are no when-not conditions or named alternatives, so it gives context but no exclusions.

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