rickandmorty-mcp

Buscar localizaciones

list_locations

Read-onlyIdempotent

Search Rick and Morty locations by name, type, or dimension. Get up to 20 results per page, each including resident IDs.

Instructions

Busca localizaciones por nombre, tipo o dimensión. Devuelve una página de hasta 20 resultados, cada uno con los ids de sus residentes.

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

Input Schema

Name	Required	Description	Default
`name`	No
`page`	No
`type`	No
`dimension`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already establish read-only, open-world, idempotent, non-destructive behavior. The description adds meaningful behavioral detail beyond that: it returns a page of up to 20 results and includes each location's resident IDs. This is useful operational context not present in annotations.

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?

The description is compact and front-loaded: the purpose and filter criteria appear first, followed by pagination and result-shape details. Every sentence earns its place with no 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?

The description covers the essential call context: search criteria, pagination limit, and result content. Since an output schema exists, detailed return-value documentation is not required. Minor gaps remain around how filters combine and whether matching is exact or partial, but the tool is still sufficiently invokable.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate. It successfully maps the three filter parameters (name, type, dimension) and implies the page parameter via 'Devuelve una página'. This provides meaningful semantics the bare schema lacks, although it does not detail filter combination behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb ('Busca') and resource ('localizaciones'), and names the filtering dimensions: name, type, and dimension. It also distinguishes itself from the sibling get_location by emphasizing search/filter over direct ID lookup.

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?

The description clearly implies when to use the tool — when searching locations by name, type, or dimension — but it does not explicitly contrast it with get_location for direct ID access or with list_characters/list_episodes for other resource types. Usage context is implied rather than explicit.

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

Deploy Server