Skip to main content
Glama

amiibo_by_series

Read-onlyIdempotent

Lists Amiibo figures for a specified game series, so you can find collectibles tied to a franchise.

Instructions

List Amiibo figures in a game series.

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": {
      "series": "<series>"
    },
    "name": "amiibo_by_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
seriesYesAmiibo series name (e.g. Super Mario, Zelda)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, covering the safety profile. The description adds nothing further — no return shape, no pagination behavior, no note on how series names are matched — so it contributes no behavioral context beyond structured data.

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?

A single tight sentence with the scope stated up front and no filler. It is appropriately sized, though it could have used one more clause to route agents away from sibling tools at no real cost.

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 trivial one-parameter list tool with complete schema coverage and rich annotations, little is strictly required. Still, no output schema exists and the description says nothing about result format, so an agent cannot anticipate what 'lists' means in practice.

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 the 'series' parameter is already documented with examples in the schema. The description only weakly restates that filtering happens by series, which is the baseline expectation for full schema coverage.

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 verb and resource are explicit ('List Amiibo figures'), and the required 'series' scope is stated. However, it does not distinguish itself from siblings like amiibo_search or amiibo_types, and 'game series' is slightly ambiguous since the parameter is actually the Amiibo series name (e.g. Super Mario).

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 guidance on when to use this versus amiibo_search or amiibo_types, and no mention of whether results are filtered, paginated, or exhaustive. The agent must infer the routing decision from the name alone.

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