Farrukh Inomov

Request an intro call

book_call

Requests a 30-minute intro call at a free time from get_available_slots. Farrukh confirms every request; Cal.com then emails the Google Meet invitation. Confirm the details with the user first.

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": {
      "name": "<name>",
      "email": "<email>",
      "company": "<company>",
      "reason": "<reason>",
      "start": "<start>",
      "timeZone": "<timeZone>"
    },
    "name": "book_call"
  }
}

Input Schema

Name	Required	Description	Default
`lang`	No	Language of the invitation: "de" or "en".	en
`link`	No	Optional link, e.g. to the job posting
`name`	Yes	Full name of the person who will join the call
`email`	Yes	Cal.com sends the invitation to this address
`start`	Yes	Start of a free slot from get_available_slots
`reason`	Yes	What the call is about, 10 to 1000 characters
`company`	Yes	Company the person works for
`timeZone`	Yes	IANA time zone of the user, e.g. "Europe/Berlin" or "America/New_York".

Output Schema

Name	Required	Description	Default
`label`	Yes
`start`	Yes
`status`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already flag this as a non-read-only, open-world, non-idempotent mutation, and the description usefully adds that Farrukh manually confirms every request and that Cal.com emails a Google Meet invitation — side effects an agent could not infer from annotations alone. It does not cover failure modes such as a slot being taken between listing and booking, or whether duplicate requests are possible.

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?

Three short sentences, front-loaded with what the tool does, followed by the confirmation flow and the closing instruction to verify details. No filler or redundant restatement of the schema.

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?

Return values are covered by the output schema and per-field meaning by the schema, so the description focuses correctly on the human-approval workflow and downstream email delivery. The remaining gap is error behavior when the requested slot is unavailable, which matters for a non-idempotent booking call.

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 every parameter is already documented, including start's link to get_available_slots and the timeZone format. The description adds only the implicit requirement that all details be user-confirmed, which is marginal beyond the schema baseline.

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?

States a specific verb (requests), resource (30-minute intro call), and the exact input source (a free time from get_available_slots). An agent can distinguish it from sibling read tools like get_available_slots or get_profile without opening the schema.

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

Usage Guidelines4/5

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

Gives clear procedural guidance: pick a free slot from get_available_slots and confirm the details with the user before submitting. It does not state when not to use it or what to do if the slot is no longer free, so it stops short of full when/when-not coverage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Farrukh Inomov tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.