Skip to main content
Glama

Thomas Anglero Speaker MCP

Get booking information

get_booking_info
Read-only

How to book Thomas Anglero, AI keynote speaker (in person and virtual). How booking works, the formats offered, and how fees are handled. Fees are provided on inquiry, tailored to format and location. Thomas replies promptly.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes this is a safe, non-mutating lookup, so the description only needs to add context. It contributes some beyond the annotation by noting fees are not listed here but supplied on inquiry, and that replies are prompt, but says nothing about the shape or depth of the returned information.

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 short sentences, front-loaded with the subject and scope, with no wasted preamble. The closing line ("Thomas replies promptly") is promotional rather than informative and does not earn its place as strongly as the rest.

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?

With no parameters and no output schema, the description needs only to tell the agent what information it yields, and it does: booking mechanics, offered formats, and fee policy. It would be marginally stronger if it stated whether this is a prerequisite step before submitting an inquiry.

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 nothing for the description to disambiguate. The schema is fully closed (additionalProperties false) and consistent with a parameterless info lookup.

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 names a specific resource (booking information for Thomas Anglero as an AI keynote speaker, in person and virtual) and enumerates what the answer covers: booking process, formats, and fee handling. It is clear what the tool returns, though it never contrasts itself with close siblings such as get_availability_guidance or get_advisory_info.

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?

Usage is only implied: the reader can infer this is the entry point for learning about booking before submitting an inquiry ("Fees are provided on inquiry"). There is no explicit statement of when to call this versus submit_speaking_inquiry or get_availability_guidance, and no prerequisites are given.

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