Skip to main content
Glama

Dodávky Znojmo

get_contact_info

Vrátí kontaktní údaje půjčovny - telefon, email, adresu, otvírací dobu a mapu.

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_contact_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. The framing ('Vrátí' — returns) implies a side-effect-free read, which is helpful, but it says nothing about caching, freshness of the data, response format, or failure behavior. For a trivial no-param getter the risk is low, so a middle score is fair.

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 and resource first and the returned fields listed after. No filler, no redundancy.

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?

There is no output schema, so the description's enumeration of return fields (phone, email, address, hours, map) is the only disclosure of what comes back — and it covers that well. Minor gap: no indication of whether the map is a URL, coordinates, or an embedded object.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description wisely spends its words on the return contents instead.

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 ('Vrátí' / returns) plus a resource ('kontaktní údaje půjčovny') and enumerates the returned fields (phone, email, address, opening hours, map). It does not explicitly differentiate itself from the siblings, but the resource is distinct enough that confusion with get_fleet_info or check_availability is unlikely.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit statement of when to use this versus alternatives; the usage is implied by the resource name alone. For a zero-parameter info lookup this is adequate, but there is no guidance such as 'use when the customer asks for location or hours' or a note that other tools supply fleet/booking data.

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