Skip to main content
Glama

Rick and Morty (Unofficial)

Rick And Morty Search Characters

rick_and_morty_search_characters
Read-onlyIdempotent

Search Rick and Morty characters by name with optional filters for status (alive/dead/unknown), species (Human/Alien/etc.), and gender. Returns up to 20 matching characters per page with status, species, origin, current location, and episode appearances.

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": "rick"
    },
    "name": "rick_and_morty_search_characters"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoCharacter name to search for (partial match, e.g., "rick", "beth")
pageNoPage number (1-based, default 1). API returns 20 per page.
genderNoFilter by gender: "female", "male", "genderless", or "unknown".
statusNoFilter by status: "alive", "dead", or "unknown".
speciesNoFilter by species (e.g., "Human", "Alien", "Mythological Creature").

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds the pagination cap of 20 per page, which is genuinely new behavioral context, but it then restates return fields that the output schema already documents. It says nothing about empty-result behavior or whether filters combine with AND semantics.

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 the action and narrowed to filters and result shape. Every clause carries information and nothing is padded.

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?

An output schema exists, so spelling out return fields was optional and the description is not penalized for brevity there. Combined with the pagination note, an agent has what it needs to call correctly; only the search-vs-get routing and filter-combination semantics are missing.

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 every parameter is already documented with types, enum-like values, and examples. The description's mentions of status values (alive/dead/unknown), species, and gender add no syntax or constraint detail beyond the schema, so the baseline of 3 applies.

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 gives a specific verb and resource ("Search Rick and Morty characters") and enumerates the filterable dimensions, so the agent knows exactly what it retrieves. It does not, however, distinguish itself from the sibling rick_and_morty_get_character, which is the obvious source of ambiguity for this tool family.

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?

Usage is only implied by the word "Search" — the agent can infer this is the list/filter tool, but nothing states when to prefer it over get_character for a known single character. No exclusions, prerequisites, or fallback guidance are given.

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.