Skip to main content
Glama

Thomas Anglero Speaker MCP

Search site content

search_site_content
Read-only

Search the verified content of anglero.com about Thomas Anglero, AI keynote speaker (in person and virtual): his keynote topics, the dated Track Record, published FAQs, evergreen guides, client testimonials and keynote videos, in English or Norwegian. Use it to answer a buyer's question from published content and to find the page to cite. Returns each match with its page URL and a short summary.

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

Input Schema

NameRequiredDescriptionDefault
langNoOptional. "nb" searches the Norwegian pages.en
typeNoOptional. Limit the search to one kind of content.
limitNoOptional. Most results to return.
queryNoWords to look for, in English or Norwegian. Optional when type is given.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the bar is lower. The description does add valuable behavior beyond them: it says each match comes back with its page URL and short summary, which matters because there is no output schema. It discloses nothing about ranking, empty-result behavior, or pagination beyond the limit parameter.

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 front-loaded sentences: scope first, use case second, return shape third. The content-type enumeration is long but each item earns its place by scoping the corpus. No filler or boilerplate.

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 output schema, the description carries the return-value burden and does so ('each match with its page URL and a short summary'). Scope, language, and use case are all present for a 4-parameter, 0-required search tool. Only minor gaps remain: how matching works (keyword vs. semantic) and what an empty result looks like.

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

Parameters3/5

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

Schema description coverage is 100%, so all four parameters are already documented in the schema. The only parameter-related content in the description ('in English or Norwegian') restates the lang enum rather than adding meaning, so the baseline of 3 is appropriate.

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 gives a specific verb ('Search') and a precisely bounded resource ('the verified content of anglero.com'), and it enumerates the covered content types (topics, Track Record, FAQs, guides, testimonials, videos) plus the two languages. What keeps it short of a 5 is that it never states how it differs from the structured getter siblings such as get_keynote_record or get_speaker_profile, so an agent facing 'record' queries must infer search-vs-retrieve on its own.

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 concrete when-to-use guidance: 'answer a buyer's question from published content' and 'find the page to cite', which tells the agent this is for answering from published material rather than for structured lookups. There is no explicit when-not guidance or named alternative tool, which is what separates it from a 5.

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