Skip to main content
Glama

digimon_by_level

Read-onlyIdempotent

Retrieve Digimon filtered by evolution level—Fresh, Rookie, Champion, Ultimate, or Mega—to find creatures at a specific stage.

Instructions

List Digimon filtered by evolution level.

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": {
      "level": "<level>"
    },
    "name": "digimon_by_level"
  }
}

Input Schema

NameRequiredDescriptionDefault
levelYesLevel: Fresh, In Training, Rookie, Champion, Ultimate, or Mega

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

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, non-destructive, and openWorldHint, so the safety profile is covered. The description adds the level-filtering scope but does not discuss result shape, ordering, or whether matching is exact/case-sensitive, so it adds only moderate behavioral context.

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?

A single front-loaded sentence with no wasted words. It immediately conveys the tool's action and filter.

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?

For a simple read-only, one-parameter listing tool with full schema coverage and annotations, the description is adequate. It could be slightly stronger if it clarified exact-match behavior or that it returns a list, but no critical information is 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%, and the single level parameter already lists all accepted values. The description merely restates that filtering is by evolution level and adds no extra semantics beyond the schema.

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 clearly states a specific verb and resource (list Digimon) plus the filtering dimension (evolution level). It does not explicitly distinguish this from sibling tools like digimon_all or digimon_by_name, so it stops short of a 5.

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 implied: call this when you need Digimon filtered by evolution level. However, it gives no explicit guidance on when to prefer it over digimon_all or digimon_by_name, and no exclusions or alternative conditions.

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