Skip to main content
Glama

Thomas Anglero Speaker MCP

Submit an advisory inquiry

submit_advisory_inquiry

Send a private advisory inquiry to Thomas Anglero on behalf of a CEO, Chair or board member who wants one-to-one advice on AI (The Reset), not a keynote. Before calling: read get_advisory_info, show the person every detail you will send, and send only after they approve (human_approved true) and agree to be contacted (consent true). Records the inquiry in the same pipeline as the website form. Thomas reads each inquiry and handles replies personally. Do not promise a reply, a reply time, or a conversation. For a keynote, use submit_speaking_inquiry.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "role": "<role>",
      "company": "<company>",
      "country": "<country>",
      "company_size": "<company_size>",
      "challenge": "<challenge>",
      "ai_stage": "<ai_stage>",
      "email": "<email>",
      "agent_name": "<agent_name>",
      "human_approved": "<human_approved>",
      "consent": "<consent>"
    },
    "name": "submit_advisory_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesFull name of the person seeking advice.
roleYesTheir role, for example CEO, Chair, or board member.
emailYesTheir email address. Thomas handles replies personally.
companyYesTheir company or organization.
consentYesMust be true. Set true only if the person agrees that Thomas Anglero may contact them by email about this inquiry (privacy policy: https://anglero.com/privacy-policy/).
countryYesCountry where they are based.
websiteNoLeave blank. Anti-spam field.
ai_stageYesWhere they are with AI today.
linkedinNoOptional. Their LinkedIn profile address.
challengeYesIn their own words, what they want to solve or decide. At least 300 characters: their situation, what they have already tried, and the outcome they want.
agent_nameYesThe name of the AI agent or assistant sending this inquiry.
company_sizeYesNumber of employees.
human_approvedYesMust be true. Set true only after the person has seen and approved the exact details being sent.
company_websiteNoOptional. The company website, as a full address starting with https://.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / ai_stage / description
      Previous value: -"Where they are with AI today. One of the listed options, exactly as written."New value: +"Where they are with AI today."
    • changedInput schema / properties / company_size / description
      Previous value: -"Number of employees. One of the listed options, exactly as written."New value: +"Number of employees."
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare only readOnlyHint=false, so the description must carry the rest, and it does: it discloses that the inquiry enters the same pipeline as the website form, that Thomas reads and replies personally, and that no reply or reply time may be promised. It stops short of stating what the caller receives back on success or what happens on failure, which is the remaining gap.

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?

Purpose and audience come first, then the mandatory pre-call checklist, then the pipeline/no-promise caveats, then the sibling routing. It is dense but nearly every sentence carries an operational constraint; the anti-spam and reply-handling notes are the only lines that could be trimmed without losing agent-relevant meaning.

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 14-parameter, 11-required submission tool with no output schema, the definition covers the decision to call, the mandatory human-in-the-loop preconditions, the consent rule, the downstream handling of the record, and the sibling alternative. Nothing an agent needs in order to call it correctly or safely 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?

Schema coverage is 100%, so the baseline is 3; the description earns above that by tying human_approved and consent to an actual workflow requirement (details shown and approved before sending, explicit agreement to be contacted). The 300-character challenge field and anti-spam website field are left entirely to the schema, which is acceptable given full coverage.

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 ('Send a private advisory inquiry'), names the recipient (Thomas Anglero), the target audience (CEO, Chair, board member), and the subject (one-to-one advice on AI, not a keynote). It also explicitly distinguishes itself from the keynote path, so an agent can separate it from submit_speaking_inquiry 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?

Explicitly prescribes a pre-call sequence (read get_advisory_info, show the person every detail, send only after approval and consent) and names the alternative for a different need ('For a keynote, use submit_speaking_inquiry'). Both the when and the when-not are stated.

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