Skip to main content
Glama

Solar-Spedition

Leistungsprofil / Service profile

get_service_profile
Read-only

Returns what Solar-Spedition (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.6/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 is covered. The description adds useful behavioral context by spelling out what the response contains (including the negative scope, 'what is not offered', and price availability), which prevents the agent from guessing. It says nothing about whether content is static or live, caching, or how the absence of prices should be interpreted.

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?

One dense sentence with no filler, and the content list is front-loaded. The key routing instruction 'Call this first' sits at the very end, where it would earn more attention at the front.

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 read-only profile tool with full annotation coverage and no output schema, the description is nearly complete: it defines the response contents and establishes the call ordering. The only real gap is the unmentioned language parameter, which is minor for an optional enum.

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 an enum of de/en and zero schema description coverage, and the description never mentions it, so the agent gets no statement that it controls the response language or what the default is. The enum constrains the values enough that the tool is still callable without it, but the description adds no meaning here.

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 a named resource ('what Solar-Spedition (Logisticoo GmbH) offers') and enumerates the concrete contents: services, what is not offered, price availability, inquiry submission, contact and legal links. That is far more specific than the bare name, though it does not name the sibling tools it precedes.

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 ordering guidance relative to the inquiry tools, which is exactly the context an agent needs at session start. It stops short of naming preview_inquiry/submit_inquiry as the follow-ups or stating any condition under which this call should be skipped.

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