Skip to main content
Glama

fs_search_series

Search TV series by name on fernsehserien.de to find matching shows and their series pages. Returns series only, not films, with an optional result limit.

Instructions

Search TV series by name on fernsehserien.de. query: e.g. babylon, tatort, breaking bad. limit: 1..20 (default 10). Films are not returned — series only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "fs_search_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden; it does disclose the limit range, the default of 10, and the films exclusion, but says nothing about result ordering, no-match behavior, or any access constraints. Those remaining gaps keep it at an adequate-but-incomplete level.

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?

Three short, front-loaded sentences covering purpose, query examples, and limit constraints, with zero filler. Nothing redundant is included.

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 two-parameter search tool with an output schema already describing returns, the description covers what matters: what is searched, what is excluded, and how to bound the limit. Only minor edge-case behavior (empty results, ordering) is unaddressed.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it largely does: query gets illustrative examples (babylon, tatort, breaking bad) and limit gets a concrete 1..20 range plus a default of 10. The default duplicates the schema, and the query format (substring vs. exact) is never clarified.

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 concrete verb and resource ('Search TV series by name') plus the target site, and adds the scope constraint that films are excluded, which separates it from detail/episode siblings. It stops short of naming which sibling to use next, but the purpose is unambiguous.

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?

Provides example queries and an explicit scope exclusion ('Films are not returned — series only'), which tells the agent when this tool is inappropriate. It does not explicitly route to fs_series_detail for follow-up, so the workflow guidance is implicit rather than spelled out.

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