compare_entities
Compare 2–5 entities across the four scoring dimensions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| slugs | Yes |
atlaxy
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.8/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the burden of disclosing behavior. It does not explain what the four scoring dimensions are, whether the operation is read-only, what output format is returned, or how the comparison is structured. It only restates the basic action.
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?
The description is a single sentence with no filler, and the core action and key constraint are front-loaded. It is concise and well structured for the limited information it conveys.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema and no annotations, the description is the sole source of context. It omits the meaning of the four scoring dimensions, the return value, and practical limitations beyond the count, leaving an agent under-informed for confident invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not explicitly define what 'slugs' refers to beyond implying they identify the entities to compare. It adds the 2–5 range constraint but omits details such as ordering, uniqueness, or entity type requirements.
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 states a specific verb ('compare') and resource ('entities'), with a clear count range and the object of comparison ('four scoring dimensions'). It differentiates from sibling tools that retrieve, list, or search single entities, though the scoring dimensions themselves are not named.
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?
No guidance is provided on when to use this tool versus get_entity, search_entities, or list_entities. The count range implies multi-entity comparison, but there is no explicit context, prerequisites, or exclusion criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.7/5.0
Disambiguation5/5
Each tool has a distinct role: get single entity, list entities, search entities, compare entities, get relations, get taxonomy, get tracks, get snapshot meta. Although list_entities and search_entities are related, their descriptions clearly separate filtering/ranking from keyword search.
Naming Consistency5/5
All tool names follow a consistent verb_noun snake_case pattern using clear verbs: get, list, search, compare. There are no mixed conventions or vague generic names.
Tool Count5/5
8 tools is well-scoped for a read-only knowledge/atlas server. Each tool covers a meaningful operation without redundancy or unnecessary bloat.
Completeness5/5
The set covers the full read-only lifecycle: discovery (list, search), detail (get_entity), analysis (compare, relations), and context (taxonomy, tracks, snapshot meta). No obvious gaps exist for the apparent purpose of exploring and comparing scored entities.