Skip to main content
Glama

explore_sensory_earth

Read-onlyIdempotent

Open the Sensory Earth globe for a city or country.

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

Input Schema

NameRequiredDescriptionDefault
languageNoLanguage (en, es, pt)es
destinationYesCity or country to explore

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/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 adds nothing beyond that: it does not explain what "open" produces, whether a session/UI is launched, or whether results are cached per destination/language. For a tool whose central verb is undefined, this is a real gap rather than a minor one, and no annotation is contradicted.

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 no filler and the scope front-loaded. It is efficient, though the brevity comes at the cost of specification rather than through tight editing of rich content.

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?

The tool is simple (one required string param, no output schema, annotations present), so the description need not explain return values. Still, the meaning of the core action is missing, which leaves an agent unable to predict what invoking it actually does.

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% with only two simple string parameters, so the schema fully carries semantics and the baseline is 3. The description reinforces that destination accepts a city or country but says nothing about the language parameter or its default of 'es'.

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 description pairs the verb "Open" with a named resource, "the Sensory Earth globe", and a scope, "for a city or country". However, "Sensory Earth globe" is a proprietary label and "Open" is ambiguous - it does not tell an agent whether this renders an interactive visualization, returns a URL, or fetches data. It also draws no boundary against siblings like discover_secret_haven 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 or when-not-to-use guidance, and no named alternative. The agent must infer that this is the visualization entry point rather than a discovery or itinerary tool entirely from the name.

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