Skip to main content
Glama

Thomas Anglero Speaker MCP

Get keynote record

get_keynote_record
Read-only

The dated record of Thomas Anglero's keynotes and appearances from the Track Record, newest first, as JSON. Each entry has its name, date or year, country or online, detail, video URL, public source URLs and the link to its place on https://anglero.com/awards-and-press/.

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_keynote_record"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the safety profile is already covered. The description adds real behavioral value: the results are ordered newest first, returned as JSON, and each entry carries name, date/year, country-or-online, detail, video URL, source URLs, and a canonical site link — effectively describing the return shape in the absence of an output schema. It stops short of disclosing result-count limits, pagination, or behavior when the record is empty.

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?

Two sentences, front-loaded with the resource and its ordering before the field enumeration. The field list is dense but each item corresponds to actual returned data, so little is wasted; a slightly tighter grouping of the field names would make it cleaner.

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 carries the full burden of explaining returns, and it does so by enumerating entry fields and noting ordering and format. The main residual gap is scale/pagination behavior for a potentially long record, which an agent might care about.

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 no parameters, so per the baseline this scores 4. The description correctly implies the tool is unfiltered and returns the full record, matching the empty input schema with no misleading hints about filtering options.

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 — the dated record of Thomas Anglero's keynotes and appearances from the Track Record — and names the ordering (newest first) and format (JSON). An agent can distinguish this from get_speaking_topics or get_speaker_profile by the emphasis on a dated, historical appearance log, though it never explicitly names those siblings as alternatives.

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 implied rather than stated: an agent can infer this is the tool for past appearances/keynote history, but there is no explicit 'use this when' clause and no exclusion pointing to a sibling tool. For a zero-parameter retrieval tool the intent is reasonably obvious, so implied guidance is sufficient but not strong.

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