list_versionsLists the three Final Fantasy Tactics releases covered by this server and how many records exist per entity kind in each. Call this first to pick a version.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full burden. It discloses the tool's output scope (three releases, record counts) but omits other behavioral traits like authentication or cost. Adequate for a simple read-only list.
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?
Two sentences with no wasted words. The first sentence states the primary function, the second provides usage guidance. Highly concise and front-loaded.
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?
The description is mostly complete for a simple tool with no parameters and no output schema. It could mention the output format briefly, but the essence is covered.
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?
No parameters exist, so baseline is 4 per guidelines. The description adds no param info, which is acceptable given zero parameters.
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 that the tool lists the three Final Fantasy Tactics releases and record counts per entity kind, which is specific and distinguishes it from sibling tools like compare_versions.
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?
Explicitly advises 'Call this first to pick a version,' providing clear guidance on when to use the tool. Does not elaborate on when not to use it, but the context implies it's a prerequisite.
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.
Each tool targets a distinct resource/action: compare_versions diffs releases, find_item_sources is a reverse-lookup, get_job/get_monster provide deep entity records, get_records is generic batch retrieval, query_equipment filters the equipment table, search resolves names to IDs, and list_versions describes the dataset. The descriptions explicitly call out when one tool should be used instead of another, so an agent should be able to pick correctly.
Most tools follow a clear lower_snake_case verb_noun pattern (get_job, get_monster, get_records, list_versions, compare_versions, find_item_sources, query_equipment). The only deviation is the bare verb search, and the retrieval verbs vary (get/find/query/list) rather than being uniform, but the pattern is still predictable.
Eight tools is a well-scoped size for a read-only game-data companion: a global search entry point, version metadata, generic batch retrieval, two deep-dive entity tools, an equipment filter, an item-source reverse lookup, and a cross-version comparator. No tool feels redundant, and every tool has a clear use case.
The server covers the main reference workflows well: discovery via search, batch retrieval via get_records, deep job/monster records, equipment shopping, item sourcing, and version comparison. However, there is no way to enumerate or filter non-equipment entity kinds (abilities, jobs, monsters, bosses, locations, consumables) without already knowing names/IDs, and compare_versions cannot identify which entities changed across versions. Those are notable gaps for a comprehensive companion server.