Skip to main content
Glama

Rick And Morty Get Character

rick_and_morty_get_character
Read-onlyIdempotent

Get a single Rick and Morty character by numeric ID. Returns name, status, species, origin, current location, episode appearances, and image URL.

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": {
      "id": 1
    },
    "name": "rick_and_morty_get_character"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCharacter ID (1-826+). Example: 1 = Rick Sanchez.

Output Schema

NameRequiredDescriptionDefault
idNoCharacter ID
urlNoAPI URL
hintNoHint message when character not found
nameNoCharacter name
typeNoCharacter type/subspecies
foundNoWhether character was found
imageNoImage URL
genderNoGender
originNoOrigin location name
statusNoStatus: alive, dead, or unknown
speciesNoSpecies name
locationNoCurrent location name
episode_idsNoEpisode IDs
episode_countNoNumber of episodes appeared in

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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=true, so the safety profile is covered without the description's help. The description adds nothing behavioral beyond that — no error behavior for out-of-range or unknown IDs, no mention that the ID space is bounded (1-826+), which matters for an open-world lookup. The second sentence mostly restates return data that the output schema already defines.

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 sentences, front-loaded with the action and scope, with no filler or hedging. The enumerated return fields in sentence two are somewhat redundant given a dedicated output schema, which is the only thing keeping it from a 5.

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?

With one required parameter at full schema coverage, rich annotations, and an output schema, the description needs only to identify the resource and access pattern, which it does. The remaining minor gap is failure behavior for invalid IDs, but overall an agent has enough to call this correctly.

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 100% and the single parameter's description already supplies the range (1-826+) and a worked example (1 = Rick Sanchez). The description only echoes "numeric ID," adding no format, boundary, or error semantics 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 ("Get a single Rick and Morty character by numeric ID") and narrows scope to single-record lookup, which implicitly separates it from the sibling search tool. It stops short of naming rick_and_morty_search_characters or stating the distinguishing condition, so it is clear but not sibling-differentiating.

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: "single ... by numeric ID" tells an agent this is a keyed lookup, so a caller with a name rather than an ID would have to infer they need the search tool instead. No explicit when-to-use, when-not-to-use, or alternative is stated.

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.