Skip to main content
Glama

lotr_characters

Read-onlyIdempotent

Search Lord of the Rings characters by name and limit results per page to locate specific characters.

Instructions

Search Lord of the Rings characters by name.

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

Input Schema

NameRequiredDescriptionDefault
nameNoCharacter name to search for
limitNoResults per page (default 10)

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, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds no further behavior: it does not say whether matching is exact/partial, how pagination interacts with limit, or what an empty result looks like, so it contributes almost nothing beyond the annotations.

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 front-loaded sentence with zero filler. It is efficient, though bordering on under-specification for a tool that could benefit from one more clause about results.

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?

The tool is simple (2 params, read-only, no output schema), but with no output schema the description should say something about what is returned (list of characters, fields, pagination behavior). It leaves the return contract entirely implicit, so it is adequate but with a clear gap.

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%, so both 'name' and 'limit' are already documented in the schema. The description adds no extra semantics such as case sensitivity or match type, so the baseline 3 is appropriate.

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 and resource ('Search Lord of the Rings characters by name'), which cleanly separates it from the lotr_books and lotr_quotes siblings. It lacks any hint of scope (all characters vs. filtered subset) but the core purpose is unmistakable.

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 when-to-use guidance, no mention of alternatives, and no exclusions. The 'by name' phrasing implies the query mode but gives no indication of when this tool is the right choice over e.g. listing characters or other search tools.

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