Skip to main content
Glama

ram_get_character

Read-onlyIdempotent

Retrieves a Rick and Morty character by ID, enabling lookups of character details for agent workflows and automation tasks.

Instructions

Get a Rick and Morty character by ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "ram_get_character"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCharacter ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds nothing beyond that: no statement about what happens with an unknown or malformed ID (null, empty result, error), and no note that it hits a live external API. With annotations carrying the load, that leaves minimal added value.

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?

One short sentence, verb and resource front-loaded, zero filler. Nothing superfluous for a single-parameter lookup tool.

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

Completeness3/5

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

For a simple one-param read with full schema coverage and complete annotations, the essentials are present. Missing are the two things an agent would still wonder about: ID format and failure behavior for a non-existent character.

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 'id' property is documented in-schema, so the baseline is 3. The description contributes only the word 'by ID' and doesn't clarify the expected ID format (numeric string, range, etc.) or whether names are accepted.

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 (Get) and resource (Rick and Morty character) with the 'by ID' qualifier that implicitly separates it from ram_search_characters. The distinction is inferable rather than explicit, so it stops short of 5.

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 guidance on when to use this versus ram_search_characters or the other ram_ tools. The 'by ID' phrasing implies a direct-lookup use case, but the agent must infer that a known ID is required and that search is the alternative.

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