Skip to main content
Glama
ask-aayan

ask-aayan

Book a call

book_call
Read-onlyIdempotent

Generates a scheduling or prefilled email link so users can arrange a call about a topic, including company details when provided.

Instructions

Gives a link to set up a call with him: his scheduling page if one is configured, otherwise an email link with the subject filled in. Use when someone wants to talk to him.

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

Input Schema

NameRequiredDescriptionDefault
topicNoWhat the call is about, e.g. "AI Engineer role". Goes into the email subject.
companyNoThe caller's company, added to the email subject.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: the tool only returns a link rather than booking anything, and it degrades to an email link with a prefilled subject when no scheduling page exists. It does not discuss permission or rate-limit considerations, but for a link generator that is minor.

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 compact sentences: the first states the output and its fallback, the second states the trigger. Nothing is redundant and the most important information (it hands back a link, it does not book) is front-loaded.

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 zero-required-parameter read tool with annotations covering safety and no output schema to explain, the description covers what an agent needs to call it and interpret the result. The one omission is that it never says the parameters are optional or only affect the email path, which matters slightly for correct invocation.

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%, and both parameters (topic, company) are documented as feeding the email subject. The description's mention that the subject is 'filled in' reinforces but does not extend that meaning, and it does not clarify that both parameters are optional or that they are irrelevant when a scheduling page exists.

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 uses a specific verb and resource ('Gives a link to set up a call') and explains both possible outputs: a scheduling page link or a mailto link. It is clearly distinguishable from the profile-reading siblings, but it never explicitly contrasts itself with get_availability, leaving a small ambiguity about which tool handles slot discovery.

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?

'Use when someone wants to talk to him' gives an explicit trigger condition, which is more than nothing. However, there are no exclusions or named alternatives, so an agent is not told whether to check get_availability first or what to do if a scheduling page is not configured beyond the fallback already described.

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