search_showsSearch TV shows by name. Returns shows with id, name, premiere date, network, genres, rating, status, and TVMaze URL.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Show name (full or partial) |
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | Number of results returned | |
| query | Yes | Search query string | |
| results | Yes | Array of matching shows |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / examplesAdded value: +[
+ {
+ "query": "Breaking Bad"
+ },
+ {
+ "query": "The Office"
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "count": {
+ "description": "Number of results returned",
+ "type": "number"
+ },
+ "query": {
+ "description": "Search query string",
+ "type": "string"
+ },
+ "results": {
+ "description": "Array of matching shows",
+ "items": {
+ "properties": {
+ "ended": {
+ "description": "End date (YYYY-MM-DD) or null",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "genres": {
+ "description": "Genre tags",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "id": {
+ "description": "TVMaze show ID",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "image": {
+ "description": "Show poster image URL",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "imdb_id": {
+ "description": "IMDb ID",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "language": {
+ "description": "Primary language",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "name": {
+ "description": "Show name",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "network": {
+ "description": "Network or web channel name",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "network_country": {
+ "description": "2-letter country code",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "official_site": {
+ "description": "Official website URL",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "premiered": {
+ "description": "Premiere date (YYYY-MM-DD)",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "rating": {
+ "description": "Average rating (0-10)",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "runtime_min": {
+ "description": "Episode runtime in minutes",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "score": {
+ "description": "Match score from search",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "status": {
+ "description": "Show status (Running, Ended)",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "summary": {
+ "description": "HTML-stripped show summary",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "tvdb_id": {
+ "description": "TheTVDB ID",
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "tvmaze_url": {
+ "description": "TVMaze show page URL",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "type": {
+ "description": "Show type (e.g., Scripted, Reality)",
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "query",
+ "count",
+ "results"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint false. Description adds specific return fields and data structure, providing behavioral context beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences with no filler. Front-loaded with action and resource. Every word serves a purpose.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Simple tool with one required param and output schema exists. Description lists all key returned fields, sufficient for an agent to understand what to expect.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with clear description of 'query' param. Description does not add extra meaning for parameter, but lists returned fields which indirectly helps. Baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description states 'Search TV shows by name' and lists returned fields. Clearly distinguishes from siblings like get_show (specific show) and search_people (people).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use or alternatives guidance. Sibling tools like get_show and search_people exist but no comparison provided. Agent must infer use case from name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.