Skip to main content
Glama

ThermoSped

Leistungsprofil / Service profile

get_service_profile
Read-only

Returns what ThermoSped (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

A4.1/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context by enumerating the content surface of the response — including negative information ('what is not offered') — which matters because there is no output schema to reveal the payload shape.

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?

A single front-loaded sentence with the directive 'Call this first' at the end so it is not lost. The content list is dense but every item (services, gaps, pricing, inquiry path, contacts, legal) maps to something an agent would otherwise ask for.

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 read-only orientation tool with no output schema, enumerating the returned content is exactly the right compensation, and the annotations handle safety. The one omission is any treatment of the `language` parameter, which leaves the caller guessing about localization behavior.

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`, enum de/en) at 0% schema description coverage, and the description never mentions it — no default language, no statement of what language the response body uses. The enum makes the parameter's intent largely self-evident, so this is a gap rather than a blocker.

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 ('Returns') and a precisely enumerated resource: services offered, services NOT offered, price availability, inquiry submission path, contact and legal links. The entity is disambiguated with both brand and legal name (ThermoSped / Logisticoo GmbH), making it clearly distinct from the sibling inquiry tools.

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 explicit sequencing guidance relative to the sibling tools (preview_inquiry, submit_inquiry), which is strong context. It stops short of naming those siblings or stating a when-not-to-use condition, so it is clear but not fully routing.

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