Skip to main content
Glama

get_feed

Read-only

Retrieve top plays with videos across all matches, filtered by player or kind, to answer requests like 'show me the best plays' or 'what did a player do lately' without scanning every match.

Instructions

The best plays that already have a video, across all matches, best first. Each item has the play (player, kind, round, tags), its match and the video_url. Use it to answer 'show me the best plays' or 'what did do lately' without walking every match.

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

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
playerNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the read-only and closed-world profile, yet the description adds real behavioral facts: results are ranked 'best first' and only include plays that already have video, which is a filtering constraint not visible in the schema. It also summarizes the item shape (play, match, video_url), though it says nothing about pagination or how 'best' is ranked.

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 core definition, then the return shape, then the usage triggers. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because an output schema exists, the description needn't explain return values, and its read-only profile is covered by annotations. However, for a simple feed tool the unexplained 'kind' filter and the unspecified meaning of 'best' ranking leave gaps an agent would hit when actually calling it.

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

Parameters2/5

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

Schema description coverage is 0% for all three parameters, so the description must carry the load. It only hints at the player filter via the example query; the 'kind' filter and the 'limit' cap (default 12, max 100) get no semantic explanation at all, leaving two of three params unexplained anywhere.

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 precise resource and scope: 'the best plays that already have a video, across all matches, best first,' which is meaningfully narrower than a generic play or match listing. An agent can distinguish this from highlight-listing or match-walking tools without opening the schema, though no sibling is named.

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?

Gives concrete trigger queries ('show me the best plays', 'what did <player> do lately') and implicitly discourages walking every match. Clear context for use, but no explicit when-not-to-use or named alternative tool.

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