Skip to main content
Glama

Baustoff-Logistik

Leistungsprofil / Service profile

get_service_profile
Read-only

Returns what Baustoff-Logistik (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 well covered. The description adds real value by disclosing the payload contents, notably that it reports which services are *not* offered and whether prices are available — unusual, decision-relevant facts that prevent downstream guessing. However, with no output schema, it does not describe structure, format, or size of the returned profile.

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 plus a short imperative call-to-action, front-loaded with what the tool returns. The colon-delimited list of contents is efficient. Slight weakness: the list is long enough that the operative "Call this first" instruction arrives last rather than first.

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 single-optional-parameter read-only profile tool, the description covers the essential questions — what comes back and when to call it. Because no output schema exists, the description does the work of enumerating return content and mostly succeeds; only the omitted language parameter and return-data shape leave minor gaps.

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 a single optional parameter, `language`, with an enum of de/en and 0% schema description coverage; the description never mentions language selection or what the default is. The enum values are largely self-explanatory, so the practical risk is low, but the description adds no meaning beyond the schema and leaves default behavior undocumented.

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 clear verb ("Returns") and enumerates the specific content of the profile: services, explicitly non-offered services, price availability, inquiry submission guidance, contact and legal links. It also names the provider entity. It does not explicitly name the sibling inquiry tools, so differentiation is achieved only indirectly through the "how to submit an inquiry" content item.

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 ordering instruction that tells the agent to invoke this before sibling tools such as preview_inquiry and submit_inquiry. There is no explicit when-not guidance or statement of what to do after, but the entry-point role is unambiguous.

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