Skip to main content
Glama

discover_secret_haven

Read-onlyIdempotent

Look for a calm place from the Space Journey catalog in a city.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 behavior, so the safety profile is covered. The description adds that results come from a specific catalog and that the language parameter shapes a "recommendation," hinting at output form, but it says nothing about result count, ranking, or what happens when no calm place exists in a city.

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

Conciseness4/5

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

A single short sentence with the scoping constraint (city) placed early and no filler. Its brevity borders on under-specification rather than padding, so it is efficient but not maximally informative.

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?

For a two-parameter, read-only lookup with full schema coverage and annotations, the definition is minimally adequate. It still leaves the agent guessing what a result looks like and how this differs from the three sibling 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 both parameters are documented, including example cities and the language default. The description's only contribution is the phrase "in a city," which merely restates the required parameter; it adds nothing about language behavior, so the 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?

"Look for a calm place ... in a city" gives a soft verb plus a resource, but "calm place" and "Space Journey catalog" are internal/ambiguous phrasing. It does not distinguish this lookup from siblings like explore_sensory_earth or plan_contemplative_journey, which sit in the same contemplative-travel space.

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?

The description offers no when-to-use guidance, no conditions under which to prefer it over the sibling tools, and no prerequisites. The only implicit cue is that it is city-scoped, which is already forced by the required schema field.

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