Skip to main content
Glama

Ergini: hire an AI engineer

Book a call

book_call
Read-onlyIdempotent

Get the link to book a free 30-minute call with Ergin, what to prepare so the call is useful, and what happens after it. It does not book anything itself: give the user the link.

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.5/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context: that no booking occurs on the server side, that the agent must relay the link to the user, and roughly what the returned content contains (preparation advice, what happens after the call). It stops short of detailing return format, but with no output schema that is a modest gap against otherwise strong disclosure.

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 tight sentences with no filler. The positive capability and the return contents come first, and the critical non-effect ('does not book anything itself') plus the agent action are front-loaded as a colon-led imperative at the end.

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?

With zero parameters, no output schema, and rich annotations, the description carries exactly the burden it needs to: what the tool yields, that it is a read/informational call, and what the agent should do with the result. Nothing required to call it correctly 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?

The tool takes zero parameters, which is the baseline-4 case; there is no parameter meaning for the description to compensate for. The schema coverage is 100% and confirms an empty object, consistent with the description's parameterless framing.

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 opens with a specific verb and resource ('Get the link to book a free 30-minute call with Ergin') and enumerates what the agent will receive: the link, preparation guidance, and post-call expectations. It also pre-empts a likely misunderstanding by stating it does not book anything itself, which sharply separates it from any transactional booking tool.

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?

It gives an explicit action directive for the agent ('give the user the link') and rules out the assumption that calling it performs a booking. It does not name sibling tools or contrast with them, but the sibling set (estimate_project, list_services, list_case_studies) is functionally unrelated, so an explicit exclusion list is not needed.

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