Skip to main content
Glama

Colin Wynd (tarvit.com)

Colin Wynd: talks, interviews and video

get_speaking_and_media
Read-onlyIdempotent

Colin Wynd's keynotes, talks, interviews, podcasts and demo videos, newest first, with dates, venues, summaries and links. Optionally filter by a keyword (e.g. "MCP", "x402", "modernization") or by type.

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

Input Schema

NameRequiredDescriptionDefault
typeNoKeynote, Talk, Interview, Podcast, Demo, Video or Short
topicNoKeyword to filter by; matches title, venue or summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower; the description still adds real value by disclosing ordering ('newest first') and the fields returned (dates, venues, summaries, links) in the absence of an output schema. It does not say whether the full set is returned or capped, which is the main 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the resource and return contents, then the optional filtering. Nothing is redundant or padded.

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?

For a two-optional-parameter read tool with full annotation coverage and no output schema, the definition covers purpose, ordering, and returned fields adequately. The only material omission is result-volume behavior (whether all items come back or a subset does).

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% and both properties already document allowed values and match behavior ('matches title, venue or summary'), so the baseline is 3. The description's example keywords ('MCP', 'x402', 'modernization') add modest guidance on what kind of term to pass, but it largely restates the filters the schema already defines.

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?

Names a specific resource set — keynotes, talks, interviews, podcasts, demo videos — and states the return contents (dates, venues, summaries, links) plus sort order. The verb is implicit in the noun phrase and in the tool name rather than stated, and no sibling (get_article, list_writing, search_writing) is named for contrast, but the domain is unmistakable.

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?

The description makes clear that both filters are optional and gives example keywords, which implicitly tells an agent it can call with no arguments. It never says when to prefer this over get_article or search_writing, nor any exclusion, so usage is only implied rather than directed.

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