Skip to main content
Glama

Lager-Logistik Berlin

Leistungsprofil / Service profile

get_service_profile
Read-only

Returns what Lager-Logistik Berlin (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.9/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 the safety profile is covered; the description then adds genuinely new information about the shape of the response, including the unusual disclosure that it reports what is NOT offered and whether prices exist. That negative-space disclosure is valuable because it prevents the agent from assuming a missing price means an error. It does not say whether the content is static or cached, but nothing material is contradicted.

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 core content is a single front-loaded sentence that spends its words on what the caller gets, followed by a short imperative 'Call this first' that lands the priority. The list is dense but each item earns its place by mapping to a distinct part of the payload. Minor deduction for the slightly awkward embedded German/company naming that adds reading cost without adding selection value.

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 zero-required-parameter, non-destructive read with no output schema, the description covers what an agent needs: what comes back, that it should be called first, and that prices may be absent. The only real gap is the unmentioned language parameter and its default, which is a small omission against an otherwise complete picture.

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 schema description coverage at 0%, so the schema documents the enum values de/en but not their effect on the returned content. The description never mentions language at all, leaving the agent to infer that it controls the output language and what the default is. The enum is largely self-documenting, which keeps this at a minimum-viable 3 rather than lower.

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 names a specific verb ('Returns') and a well-scoped resource, then enumerates the exact payload: services offered, services explicitly not offered, price availability, inquiry submission path, contact and legal links. That enumeration makes the tool unmistakable. It does not explicitly name the sibling tools or contrast itself with them, which keeps it short of a 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, actionable sequencing instruction that tells the agent to anchor on this profile before doing anything else, notably before preview_inquiry or submit_inquiry. It gives no explicit when-not-to-call condition or named alternative, so it stops short of the 5 bar.

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