Skip to main content
Glama

Mia Amare - DJane

Booking link for DJ Mia Amare

buchungslink
Read-only

Returns a pre-filled booking form URL for a festival organiser who wants to book DJ Mia Amare. Does not send anything.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "festival": "<festival>"
    },
    "name": "buchungslink"
  }
}

Input Schema

NameRequiredDescriptionDefault
bisNo
ortNo
vonNoYYYY-MM-DD
langNo
festivalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description usefully reinforces this with 'Does not send anything' — resolving the likely agent worry that generating a booking link might contact the artist or submit a request. It stops short of covering whether links expire, require authentication, or how the pre-filling behaves.

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, front-loaded with the return value and scope, with the side-effect clarification second. Nothing is wasted or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With five parameters at 20% schema coverage and no output schema, the description should explain the parameter roles and what the returned URL looks like. It covers purpose and safety but leaves the bulk of the calling contract undocumented.

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

Parameters2/5

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

Schema description coverage is only 20% (only 'von' carries a format note), and the description adds no meaning for bis, ort, lang, or festival. The agent must guess what the required 'festival' expects and what the date/place/language fields control in the pre-filled form.

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?

States a specific verb and output ('Returns a pre-filled booking form URL') for a specific resource ('booking DJ Mia Amare'), so the agent knows exactly what it gets. It does not explicitly position itself against siblings like mia_amare_info or festivals_suchen, but the purpose is unambiguous on its own.

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?

The audience is implied ('a festival organiser who wants to book DJ Mia Amare'), which suggests when to use it, but there is no explicit when-not guidance or named alternative for related needs such as looking up artist info or finding festivals.

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