Skip to main content
Glama

Link to a place on the globe

view_link
Read-onlyIdempotent

Makes a www.ortho-earth.com link that opens the 3D globe at a place, and the matching view string for createGlobe({ view }). zoom uses the same scale as the view string (about 0–2 for the whole Earth, 12 for a city). app "japan" adds Japan's detailed basemap and PLATEAU 3D buildings.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "view_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoglobe
latYes
lonYes
zoomNo
pitchNoTilt in degrees
bearingNoRotation in degrees, clockwise from north

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered and the description's extra context is genuinely additive: it explains the two return artifacts (an external URL and a view string) and clarifies that zoom shares the same scale as the view string. That return-shape disclosure goes beyond what the annotations already tell the agent. The description does not, however, mention any URL length limits, encoding behavior, or whether coordinates are rounded.

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?

Only three sentences, with the primary output stated first and the parameter hints following, so the most important information is front-loaded. The zoom and app clamp together into one dense trailing sentence, which is slightly run-on but every clause contributes concrete information rather than 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 6-parameter, no-output-schema tool, the description covers what is produced (link plus view string), the scale of zoom, and the effect of the app enum, so an agent can call it confidently. Gaps remain around the exact link format, whether invalid coordinates are rejected, and whether the URL is meant to be embedded or handed to a user, but none of those block a correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With schema description coverage at only 33%, the description carries most of the burden, and it does so well: it defines zoom semantics with a concrete scale, explains that app "japan" adds Japan's detailed basemap and PLATEAU 3D buildings, and clarifies the relationship between zoom and the view string. It adds nothing for lat/lon or pitch and bearing, but those are self-describing via schema ranges and inline descriptions ('Tilt in degrees', 'Rotation in degrees, clockwise from north').

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?

The description names a concrete verb and artifact: it produces a www.ortho-earth.com link that opens a 3D globe at a place, plus the matching view string for createGlobe({ view }). No sibling (check_compat, get_facts, lookup_api, search_docs, etc.) produces links, so an agent can identify this tool's role without opening a schema.

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?

Usage is only implied by the domain framing rather than stated outright: it never says when an agent should build a link versus calling lookup_api or get_facts, and it offers no exclusions. The zoom guidance ('0–2 for the whole Earth, 12 for a city') and the note that app "japan" adds a basemap are practical hints that partially compensate, but nowhere is an explicit when-to-use condition spelled out.

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.