Skip to main content
Glama

Compare resorts

compare_resorts
Read-onlyIdempotent

Side-by-side comparison of 2-6 properties on a fixed attribute set (location, transfers, scale, board, tier, experience tags).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slugs": "<slugs>"
    },
    "name": "compare_resorts"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugsYes2-6 canonical property slugs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description usefully discloses that comparison is restricted to a *fixed* attribute set rather than arbitrary fields, but says nothing about behavior on invalid/duplicate slugs or fewer than two entries.

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?

One sentence, no filler, and the core operation is front-loaded before the attribute list. Every clause earns its place.

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

Completeness4/5

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

With no output schema, the description carries the burden of describing returns and does so by enumerating the compared attributes. The only shortfall is that error/edge behavior (unknown slug, too few items) is unaddressed, which is minor for a simple idempotent read.

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% and the single 'slugs' parameter already documents the 2-6 constraint, so the description adds no syntax or format detail beyond the schema. Baseline 3 applies when the schema does all parameter work.

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?

Names a specific operation (side-by-side comparison) on a specific resource (resorts/properties) with an explicit cardinality bound of 2-6. The enumerated attribute set (location, transfers, scale, board, tier, experience tags) makes it clearly distinguishable from single-property siblings like get_resort or similar_resorts.

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

Usage Guidelines3/5

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

The 'side-by-side comparison of 2-6 properties' phrasing implies the usage context (multiple known candidates) but never states when to prefer this over get_resort, similar_resorts, or search_resorts. No exclusions or prerequisites are given, so routing is left to inference.

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.

Resources