Skip to main content
Glama

ram_search_episodes

Read-onlyIdempotent

Search Rick and Morty episodes by name or episode code, such as S01E01, to locate the specific episode you need.

Instructions

Search Rick and Morty episodes by name or episode code.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
pageNo
episode_codeNoe.g. S01E01

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive behavior, so the safety profile is covered. The description adds nothing about result limits, pagination behavior, or whether matching is exact or partial — the remaining behavioral questions an agent would have.

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?

A single front-loaded sentence with no filler. It is efficient, though so terse that it has no room for the pagination and matching details an agent would benefit from.

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

Completeness2/5

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

With three parameters, low schema description coverage and no output schema, the description should say more: what a result looks like, how 'page' behaves, and whether multiple pages exist. It covers only the search keys, leaving meaningful gaps for correct invocation.

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

Parameters3/5

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

Schema coverage is only 33%, with the one described parameter being episode_code ('e.g. S01E01'). The description confirms that name and episode_code are the search keys, but leaves 'page' completely unaddressed in both schema and description, and doesn't say whether name is a substring or exact match.

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 specific verb (search) and resource (Rick and Morty episodes) and names the two lookup keys. An agent can distinguish it from ram_get_episode by inference (search vs. fetch by id), though the sibling is never named explicitly.

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?

'Search ... by name or episode code' implies the trigger condition (you have a title or a code like S01E01). However, it never says when to prefer this over ram_get_episode, whether parameters can be combined, or what happens with an empty query.

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

Deploy Server

Other Tools