Skip to main content
Glama

discover_secret_haven

Read-onlyIdempotent

Find hidden cultural sanctuaries, quiet courtyards, secluded gardens, and viewpoints in a city. Get a secret alternative near a crowded landmark based on your preferred atmosphere.

Instructions

Discover intimate, secret cultural sanctuaries and hidden local gems where time slows down. Reveals the untold stories, peaceful courtyards, secluded gardens, and breathtaking viewpoints that transform an ordinary trip into a lifelong memory.

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

Input Schema

NameRequiredDescriptionDefault
cityYesCity name (Rome, Paris, CDMX, Tokyo, etc.)
languageNoLanguage for the recommendation (en, es, pt)es
sensory_preferenceNoAtmosphere preference (historic courtyards, secret gardens, serene viewpoints, artistic retreats)historic courtyards
current_crowded_spotNoCurrent landmark or busy area to discover a secret alternative nearby

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.9.4

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that results are experiential recommendations (stories, courtyards, gardens, viewpoints), which is modestly useful, but it says nothing about result count, ranking, personalization, or output shape. With annotations carrying the safety burden, this is adequate but thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

At two sentences it is appropriately short and front-loads the core idea, so it is not bloated. However, the second sentence is entirely atmospheric filler ('transform an ordinary trip into a lifelong memory') that conveys no capability, and the first spends most of its words on adjectives rather than function.

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

Completeness3/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 must hint at what comes back; it does so only vaguely by listing the kinds of places/stories returned. For a simple read-only tool with full schema coverage and clear annotations, this is minimally sufficient, but an agent still cannot tell what a response looks like or how many recommendations to expect.

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 description coverage is 100%, so city, language, sensory_preference, and current_crowded_spot are already documented in the schema. The description's mention of 'peaceful courtyards, secluded gardens, and breathtaking viewpoints' loosely echoes the sensory_preference values but adds no semantics beyond them, and it never mentions the crowded-spot-alternative behavior. Baseline 3 applies.

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

Purpose3/5

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

The verb 'Discover' plus the object 'secret cultural sanctuaries and hidden local gems' gives a rough sense of a recommendation/discovery tool, but the language is marketing copy rather than a functional statement. It never says whether it returns places, narrative stories, or a list of recommendations, and it does not distinguish itself from siblings like explore_sensory_earth or plan_contemplative_journey.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives such as explore_sensory_earth, which appears to be the closest sibling. The phrase 'transform an ordinary trip into a lifelong memory' implies a travel-planning context but gives an agent nothing actionable about when to select this tool.

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