Skip to main content
Glama

Logisticoo Heavy & Project

Leistungsprofil / Service profile

get_service_profile
Read-only

Returns what Logisticoo Heavy & Project (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 the safety profile needs no restating. The description adds useful content-shape context by disclosing that it reports what is NOT offered and whether prices exist — a meaningful expectation-setting detail — but nothing about freshness, caching, or response size for what appears to be a static profile.

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?

A single front-loaded sentence with the verb first, a tight enumeration of returned content, and a short imperative directive. Every clause carries information; no filler or restated title.

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 correctly compensates by enumerating what the return contains, which is exactly the right move for a profile/introspection tool. The only omission is any note on the language parameter's effect on the response, a minor gap for a one-optional-param read.

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%, and the description never mentions the sole `language` parameter. Mitigating factor: the parameter is a two-value enum (de/en) whose semantics are self-evident from the schema, so the practical gap is small — but the description does not state a default or what happens when language is omitted.

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?

"Returns what Logisticoo Heavy & Project ... offers" names a specific verb and resource, and the clause list (services, non-offered services, price availability, inquiry process, contact/legal links) pins down the payload precisely. It is distinguishable from preview_inquiry/submit_inquiry, though it never names them; the differentiation comes only from the implied sequencing in "Call this first."

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 explicit, actionable ordering guidance that tells the agent when this tool should be invoked relative to everything else. It stops short of stating when NOT to use it or naming submit_inquiry as the downstream step, so the routing is clear but not fully closed.

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