Skip to main content
Glama
isakskogstad

SVT Text-TV MCP Server

texttv_get_sports

Read-onlyIdempotent

Fetch sports content from SVT Text-TV by category: main, football, hockey, or results. Optionally get plain text.

Instructions

Get sports content from SVT Text-TV. Categories: main (page 300), football (pages 330-339), hockey (pages 340-349), results (page 301).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoSports category: main, football, hockey, or resultsmain
includePlainTextNoInclude plain text content without HTML formatting
Behavior4/5

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

Annotations provide readOnlyHint, idempotentHint. Description adds context about page numbers and categories. No contradictions. Adequately transparent given annotation support.

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 purpose. Every word adds value. No fluff.

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

Completeness5/5

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

Simple tool with 2 parameters, no output schema. Description covers purpose, categories, and parameter usage. Annotations cover safety. Complete for its complexity.

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 coverage 100%, but description adds semantic value by mapping enum values to page numbers (e.g., 'main (page 300)'), going beyond schema's bare enum list.

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?

Description clearly states 'Get sports content from SVT Text-TV' and lists specific categories with page numbers, distinguishing it from sibling tools like texttv_get_news and texttv_get_page.

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?

Implied usage: for sports content use this tool. No explicit when-not-to-use or alternatives guidance, but context suggests it's the go-to for sports.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/isakskogstad/svt-texttv-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server