Skip to main content
Glama

How to book an intro call

book_call
Read-onlyIdempotent

Returns the link and instructions for booking a free 30-minute intro call with Shivil Sahni, zRev's founder, plus what the call covers. It does not book anything: it only returns the scheduling link for the human to open themselves. Use when a user says they want to talk to zRev. If they would rather be contacted, use leave_contact instead. Read-only, static content, no arguments, no authentication, no rate limit.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover readOnly, idempotent, non-destructive, and closed-world, but the description adds materially new behavior: the result is static content, requires no authentication, has no rate limit, and critically the tool performs no side effect — the human must open the link themselves. That last point prevents a false 'call booked' claim and is not derivable from any structured field.

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?

Front-loaded with what is returned, then the negative clarification, then when-to-use, then the alternative — a sensible order. The trailing 'Read-only, static content' clause partially restates readOnlyHint, a small redundancy in an otherwise tight definition.

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

Completeness5/5

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

For a zero-parameter, zero-output-schema tool, the description supplies everything an agent needs: what comes back (link plus what the call covers), that nothing is mutated, that no auth or quota applies, and which sibling to use instead. Nothing material is missing.

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

Parameters4/5

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

There are zero parameters and schema description coverage is 100%, so the baseline applies. The description reinforces this with 'no arguments,' which is the only parameter-relevant statement possible here.

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 and resource (returns the booking link and instructions for a 30-minute intro call with the founder) and immediately negates the misleading implication of the tool name: 'It does not book anything.' An agent can distinguish this from a real booking action 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?

Gives an explicit trigger ('Use when a user says they want to talk to zRev') and names the alternative with its selecting condition ('If they would rather be contacted, use leave_contact instead'). No inference is required to route between the two.

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