Skip to main content
Glama

Rick and Morty (Unofficial)

Rick And Morty Search Episodes

rick_and_morty_search_episodes
Read-onlyIdempotent

Search Rick and Morty episodes by name or episode code (S01E03 style). Returns episode metadata including air date, character list, and ID.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "Pilot"
    },
    "name": "rick_and_morty_search_episodes"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoEpisode name to search for (partial match).
pageNoPage number (1-based, default 1).
episodeNoEpisode code (e.g., "S01E03").

Output Schema

NameRequiredDescriptionDefault
hintNoHint message when no results found
pageNoCurrent page number
countNoNumber of matching episodes
foundNoWhether any episodes matched the search
pagesNoTotal number of pages
totalNoTotal number of matching episodes
episodesNoList of matching episodes
has_moreNoWhether there are more pages

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile needs no restatement. The description adds that results include air date and character list, but with an output schema present that is largely redundant, and it omits useful behavior such as case sensitivity, fuzzy matching scope, and pagination semantics.

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?

Two tight sentences with the search keys front-loaded and no filler. The second sentence restates return fields that the output schema already covers, which is the only redundancy.

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 read-only search with full schema coverage, an output schema, and complete annotations, this is close to sufficient. The main missing piece is the no-filter case and whether results are paginated, which matters given the optional page parameter.

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 description coverage is 100%, so both name (partial match) and episode (S01E03 format) are already documented in the schema; the description only echoes the episode code format. The page parameter, which controls pagination, gets no mention at all in the description.

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?

The description pairs a specific verb (search) with a specific resource (Rick and Morty episodes) and names the two lookup keys, name and episode code. It is immediately clear what the tool does, though it does not distinguish itself from the sibling get_episode, which plausibly fetches a single episode by ID.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative such as get_episode for direct ID lookup. Notably, all three parameters are optional, so the description should say what happens when the caller supplies neither name nor episode — presumably an unfiltered list — but it is silent on this.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.