Skip to main content
Glama

Free intro call slots

get_intro_slots
Read-onlyIdempotent

Free slots for a free 30-minute video intro call with the Klarframe founders (Monday to Friday afternoons, Madrid time). Returns ISO start times.

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

Input Schema

NameRequiredDescriptionDefault
daysNoHow many bookable days to return
langNoAnswer language: de, en, es or it. Defaults to de.de
timezoneNoIANA time zone for the readable labels, e.g. Europe/Berlin. Defaults to Europe/Madrid.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so the description is not carrying the safety burden. It still adds real context beyond them: the call length, the founders as counterparties, the weekday-afternoon availability constraint, the timezone convention, and that results are ISO start times. It stops short of saying what happens when no slots exist within the window or how many slots come back per day.

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?

Two compact sentences with the core purpose and the return format front-loaded; every clause carries information. Minor redundancy from 'Free slots for a free 30-minute' repeating 'free', which is the only real trim available.

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 zero required parameters, a fully described schema, and annotations covering the safety profile, the definition covers what an agent needs to call it correctly, and it even states the return format in lieu of an output schema. The one gap is edge-case behavior when the requested day range yields no availability.

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?

Schema description coverage is 100%, so days, lang, and timezone are already fully documented with defaults, bounds, and an enum. The description adds no parameter-level meaning (it doesn't connect the timezone param to the 'readable labels' or note that lang only affects labels, not the ISO times). Baseline 3 applies when the schema does all the work.

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 gives a specific verb+resource ('Free slots for a ... 30-minute video intro call') and pins down scope with the availability window (Mon–Fri afternoons, Madrid time) and the return type (ISO start times). It implicitly separates itself from prepare_intro_call by being the read-only slot lookup, but it never names the sibling or explicitly contrasts with it.

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 only implied: an agent can infer this is the discovery step before prepare_intro_call, but the description contains no 'use this when' statement, no prerequisites, and no exclusions. Nothing is misleading, but the agent must reason about the workflow rather than read it.

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