Skip to main content
Glama
welt-mcp

welt-mcp

welt_latest_videos

Fetch WELT video feed items in reverse chronological order, with a configurable result limit from 1 to 50.

Instructions

Latest WELT video items from the RSS feed (subtype "video"), newest first. limit: 1..50 (default 10).

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose meaningful traits: the data source (RSS feed), the fixed subtype filter (video), the sort order (newest first), and the limit bounds. It says nothing about freshness/latency of the feed, pagination beyond the limit, error behavior, or whether results are cached.

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 short sentences, front-loaded with the resource and scope, with the limit constraint appended compactly. No wasted wording; the parenthetical subtype note is slightly awkward but earns its place as the filter definition.

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?

A simple one-parameter listing tool with an output schema, so return values need no explanation. Source, filter, ordering, and limit bounds are all covered; only feed freshness and pagination semantics are unaddressed, which is a minor gap at this complexity.

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 0% — the limit property has only a type and default, no description. The description partially compensates by stating the valid range 1..50 and restating the default of 10, which the schema does not constrain. However, it does not explain what happens with out-of-range values or whether limit affects ordering.

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?

States a specific verb+resource: latest WELT video items from the RSS feed, filtered to subtype "video", newest first. The content type (video) is distinct from siblings like welt_headlines or welt_search_news, though the description never explicitly names an alternative to route away from.

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 only implied by the words "latest" and "newest first" — an agent can infer this is the recency-oriented listing for video content. There is no explicit when-to-use/when-not statement and no named alternative (e.g., welt_search_news for keyword queries).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.