Skip to main content
Glama

Latest VODs

get_latest_vods

List the most recent Taren Raider videos with title, publish date, and watch URL. Use this when asked about recent content, VODs, or what to watch. Optionally limit the number of results between 1 and 20 (default 5).

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of videos to return, between 1 and 20. Defaults to 5.

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?

No annotations are provided, so the description carries the full behavioral burden. It discloses the returned fields and the default result count, and 'List' implies a safe read, but it says nothing about ordering guarantees, rate limits, or behavior when no videos exist.

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 tight sentences with the core action front-loaded and no filler. The final sentence largely duplicates the schema's limit documentation, which is the only minor redundancy.

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 usefully enumerates the returned fields, and it explains the optional limit. For a one-parameter read-only list tool this is nearly sufficient, missing only edge-case behavior.

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 coverage is 100% and the single parameter's bounds and default are fully documented in the schema. The description restates the same 1-20 range and default of 5 without adding any new semantics, so the baseline 3 is correct.

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 verb ('List') and resource ('most recent Taren Raider videos') and even enumerates the returned fields (title, publish date, watch URL). It is clearly distinct from siblings like get_live_status and get_schedule, though it never explicitly contrasts itself with them.

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?

'Use this when asked about recent content, VODs, or what to watch' gives a clear triggering context an agent can match against user intent. It offers no exclusions or named alternatives, so it stops short of full routing guidance.

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