Skip to main content
Glama

FFT Companion

by app.fftcompanion

Diff a record across releases

compare_versions

Compares the same entity across psx, wotl and ic and reports exactly which fields changed. Answers questions like "was this weapon nerfed in War of the Lions?" or "did Ivalice Chronicles lift the female-only restriction?" that otherwise require holding three datasets side by side. Free while this deployment runs unmetered.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesEntity id, present in at least one version.
kindYes
versionsNoWhich releases to compare.

TDQS

A4.3/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It clarifies the tool is read-only (compares, not modifies), reports exact field changes, and requires entity id and kind. Lacks details on edge cases like missing entities but overall transparent.

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?

Three sentences, front-loaded with purpose and examples, no redundancy. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 3 params, no output schema, and complexity of cross-version diffing, the description covers purpose, usage, and output format (reports field changes). Examples and sibling differentiation make it complete.

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 67% (2 of 3 params described). Description adds value through examples and context, but does not significantly expand beyond schema descriptions for id, kind, and versions. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description explicitly states it compares an entity across psx, wotl, and ic releases and reports field changes, with concrete examples like weapon nerfs or restrictions. Distinguishes from sibling tools by focusing on cross-version diffing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Clearly states when to use (comparing across releases) with examples, and mentions it's free while unmetered. Does not explicitly list when not to use or alternatives, but context is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FFT Companion toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0
Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness3/5

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.

Resources