Skip to main content
Glama

NASTARTUJTO.cz & STARTITUP.io – Free Website Proposal & B2B AI OS

book_founder_consultation

Domluvení 15minutové úvodní konzultace ZDARMA se zakladatelem Zbyňkem Melounem (+420 725 380 930). Povinný krok u zakázkových systémů vyžadujících vlastní dedikovanou databázi (Startitup NEXUS – ERP, CRM, portály na míru) a volitelný krok před objednávkou webu. V režimu mode='check_slots' vrátí 2 ověřené volné termíny z Google Kalendáře (typicky 10:00 a 14:00); v režimu mode='confirm_booking' termín rovnou napevno zapíše do kalendáře.

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": {
      "mode": "<mode>"
    },
    "name": "book_founder_consultation"
  }
}

Input Schema

NameRequiredDescriptionDefault
icoNoIČO firmy.
modeYesNejprve zavolejte 'check_slots' pro zjištění volných termínů, po odsouhlasení majitelem zavolejte 'confirm_booking'.
domainNoDoména firmy.
ownerNameNoJméno a příjmení majitele firmy (povinné při confirm_booking).
ownerEmailNoE-mail majitele firmy (povinné při confirm_booking).
ownerPhoneNoTelefon majitele firmy (povinné při confirm_booking).
companyNameNoNázev firmy.
topicSummaryNoStručný popis toho, co chce majitel probrat (nebo specifikace NEXUS systému).
callerAgentNameNo
proposedSlotIsoNoVybraný ISO termín ze seznamu volných slotů (povinné při mode='confirm_booking').
conversationHistoryNo
isNexusCustomDbSystemNoTrue pokud jde o poptávku zakázkového podnikového systému s vlastní DB (typ NEXUS).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does disclose the key behavioral facts: the consultation is free, check_slots reads Google Calendar and returns two verified slots (typically 10:00 and 14:00), and confirm_booking performs a real, firm write into the calendar. It does not say whether a confirmation email or notification goes to the owner or founder, nor the timezone or cancellation path — relevant gaps for an unannotated mutation tool.

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?

Three dense sentences ordered purpose → when required/optional → mode behavior, so the critical routing information is front-loaded. The founder's phone number in the first sentence is the one element that does not help an agent decide or call the tool, a minor inefficiency.

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 12-parameter, unannotated tool with no output schema, the description covers purpose, gating conditions, mode sequencing, and the shape of the check_slots result. It stops short of describing what confirm_booking returns (confirmation details, whether the owner is contacted) and leaves timezone/irreversibility unstated, which is the main remaining hole given there is no output schema to fall back on.

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 coverage is high (83%), so the schema already documents the twelve parameters, including the mode enum and the confirm_booking prerequisites. The description adds only a small increment over that — what check_slots returns and that confirm_booking writes the slot — which largely restates the mode field's own description rather than explaining the other inputs.

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?

The description names a concrete verb+resource (arranging a 15-minute free introductory consultation with the founder) and immediately qualifies its scope: mandatory for custom systems needing a dedicated DB (NEXUS ERP/CRM/bespoke portals), optional before ordering a website. That scope statement lets an agent distinguish this tool from website-proposal and quote siblings without opening any schema.

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

Usage Guidelines5/5

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

It states explicitly when the tool is required versus optional ('Povinný krok u zakázkových systémů... a volitelný krok před objednávkou webu'), and the mode sentence enforces sequencing: call check_slots first, only then confirm_booking. The schema's mode description reinforces the same order, so there is no ambiguity about which mode to use when.

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