charactersSearch and list ASOIAF characters filterable by name, culture, birth/death descriptor, gender, and alive status; returns aliases, titles, house affiliations, and book/POV appearances.
| Name | Required | Description | Default |
|---|---|---|---|
| born | No | ||
| died | No | ||
| name | No | ||
| page | No | ||
| gender | No | ||
| culture | No | ||
| isAlive | No | ||
| pageSize | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / examplesAdded value: +[
+ {
+ "name": "Jon Snow"
+ },
+ {
+ "culture": "Northmen",
+ "gender": "Male",
+ "isAlive": true,
+ "page": 1,
+ "pageSize": 20
+ }
+]Output schema / (root)Previous value: -nullNew value: +{
+ "description": "List of characters from A Song of Ice and Fire",
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=true, and the description does not contradict them. It adds value by mentioning return fields (aliases, titles, house affiliations, appearances) but does not disclose other behavioral aspects like pagination limits, default ordering, or filtering nuances (e.g., exact vs partial matches).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, front-loaded with the action and resource, and every part contributes meaning. It is concise without wasting words on irrelevant details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 8 parameters, 0 required, and an output schema, the description covers the core purpose and main filters. However, it leaves out essential context like pagination (page/pageSize), which is critical for a list endpoint, and the ambiguous 'birth/death descriptor' could mislead users. The output schema likely covers return values, but the input semantics remain incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 lists filterable attributes (name, culture, birth/death descriptor, gender, alive status) but does not explain parameter formats (e.g., what 'birth/death descriptor' means, whether 'gender' requires exact casing), nor does it mention pagination parameters (page, pageSize). This gives a general sense but leaves ambiguity.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with a specific verb ('Search and list') and resource ('ASOIAF characters'), and distinguishes it from sibling tools like 'character', 'house', and 'book' by indicating it handles character lists and filtering.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use the tool (searching/filtering characters) but does not explicitly mention alternatives or exclusions. It provides clear context but lacks guidance such as 'use character for single entity details' or 'use book for book-specific queries'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.