Skip to main content
Glama

Fair & Event Logistics

Leistungsprofil / Service profile

get_service_profile
Read-only

Returns what Fair & Event Logistics (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, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavioral content: that the result includes negative information (what is NOT offered) and price availability, which an agent would otherwise not expect from a profile endpoint. It does not mention freshness, auth, or rate limits, keeping it below the top band.

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 — no filler, and the content list is front-loaded. The ordering cue ("Call this first") would be stronger at the very start, and the parenthetical legal name is mild noise, but nothing is wasted.

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 carries the burden of describing return content and does so by enumerating the profile sections, including the unusual negative-offer information. Missing only the effect/default of the language parameter and any hint about response structure, which is acceptable for a single-parameter read tool.

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?

The single `language` parameter has 0% schema description coverage and is never mentioned in the description, so nothing explains whether it controls the response locale or a default. The de/en enum is largely self-documenting, which keeps this from being a real failure, but the description does not compensate for the coverage gap as required at low coverage.

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?

A specific verb ("Returns") bound to a specific resource (the company's offering), then enumerated: services, non-offered services, price availability, inquiry path, contact and legal links. An agent can tell this is a company/capability overview rather than an inquiry action, which separates it from preview_inquiry and submit_inquiry.

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 sibling inquiry tools, which is exactly the routing signal an agent needs. It stops short of stating exclusions (e.g. when to skip straight to submit_inquiry if the agent already knows the offering), so it is clear but not exhaustive.

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