Skip to main content
Glama

find_resort

Find a ski resort by name and return its numeric id (pass to get_resort_conditions and get_resort_cards) plus its page url.

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": {
      "name": "<name>"
    },
    "name": "find_resort"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesResort name, e.g. 'Chamonix'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose the return shape (numeric id and page url) and the downstream consumers. It is silent on lookup semantics (exact vs fuzzy/partial match), what happens when no resort matches (error vs empty result), and whether results are unique — meaningful gaps for a resolver tool.

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 dense sentence that front-loads the action, states the return value, and names the downstream tools. Every clause earns its place with no filler.

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?

For a one-parameter lookup with no output schema, describing the return fields (id, url) is the right call and it is done here. The only missing piece is failure/no-match behavior, which matters for a resolver whose id feeds other tools.

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 schema already supplies an example ('Chamonix') for the single name parameter. The description's 'by name' merely restates the schema, adding no syntax, casing, or matching-behavior detail beyond it, so the baseline 3 applies.

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?

States a specific verb and resource ('Find a ski resort by name') and additionally specifies the return payload (numeric id plus page url), which no other sibling tool provides. An agent can immediately tell this is a name-to-id resolver distinct from get_resort_conditions and get_resort_cards, which it explicitly names as consumers.

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?

Implicitly but clearly signals the workflow: call this first, then pass the returned id to get_resort_conditions and get_resort_cards. It does not state when NOT to use it (e.g., when the id is already known, or when a broader search is needed), so it falls short of explicit alternatives/exclusions.

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