Skip to main content
Glama

tabii_homepage

Fetches tabii's current homepage sections—exclusive content, series, movies, documentary, and kids—with each title's ID, slug, localized title, and short description for a chosen language.

Instructions

tabii's current homepage sections: exclusive content, series, movies, documentary and kids — each with its titles (id, slug, localized title, short description). language: "tr" (default), "en", "es", "ar" or "ur". No arguments besides language.

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

Input Schema

NameRequiredDescriptionDefault
languageNotr

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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. It discloses the returned section types and title fields and notes that no arguments besides language are accepted, but it does not explicitly confirm read-only behavior, auth requirements, rate limits, or how current the homepage data is.

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?

The description is two sentences, front-loads the purpose, then covers output fields and the language parameter. It is efficient overall, though listing the title fields is somewhat redundant because an output schema exists.

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 simple one-parameter retrieval tool with an output schema, the definition covers purpose, section scope, output fields, accepted language values, and default. The main missing piece is explicit routing guidance against sibling content-discovery tools.

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

Parameters5/5

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

Schema description coverage is 0% and the schema defines language only as a plain string with default 'tr'. The description compensates fully by listing the accepted values 'tr', 'en', 'es', 'ar', and 'ur', noting the default, and clarifying there are no other arguments.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific resource and scope: tabii's current homepage sections, enumerating the section types and the title fields returned. This clearly distinguishes a homepage-listing operation from sibling tools such as search or get_show.

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 implied by 'current homepage sections', so an agent can infer this is for homepage browsing rather than search or entity lookup. However, the description does not explicitly say when to use this versus tabii_search_content or tabii_get_show, and gives no exclusions.

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