Skip to main content
Glama

How to request a consultation

consultation_link
Read-onlyIdempotent

The form and phone numbers for a free first consultation. The person sends the enquiry themselves; this server cannot book or send anything.

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": "consultation_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
localeNoLanguage of the answer: de (German) or en (English).de

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description contributes a genuinely useful behavioral boundary beyond that: the server only surfaces contact channels, and the user must send the enquiry themselves. It stops short of saying what the returned payload looks like, which keeps it from a 5.

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?

Two short sentences, zero filler. The core resource is front-loaded and the capability limit follows immediately as a qualifier.

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 trivial one-parameter read tool with full annotation coverage and no output schema, the description covers enough to select and call it correctly. The remaining gap is minor: whether the response arrives as a URL, formatted addresses, or plain text is left unspecified.

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 whose schema description already states the de/en meaning and default, giving 100% coverage. The description adds nothing about the locale parameter, so the baseline of 3 applies — the schema does all the work 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 names the concrete resource — the web form and phone numbers needed to request a free first consultation — which is clearly distinct from siblings like read_guide_article or check_service_area. It lacks an explicit verb ("returns"/"provides"), but the noun phrase is specific enough that an agent knows what to expect.

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?

Usage is implied by "free first consultation" — a user wanting to make contact should come here. The description also states a boundary ("this server cannot book or send anything"), which implicitly excludes using it for booking. However, no sibling is named as the alternative for adjacent needs, and no conditions or prerequisites are spelled out.

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