Skip to main content
Glama

Tested recipe for a page with the globe

get_started
Read-onlyIdempotent

The step-by-step recipe for putting the Ortho Earth globe in a web page, with the exact file contents. Every step is run by an automated test against the published npm packages. route "vite" = npm + Vite project with @ortho-earth/globe (recommended); route "html" = a plain HTML page without a bundler.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_started"
  }
}

Input Schema

NameRequiredDescriptionDefault
routeNovite

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/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 genuinely new behavioral context: the recipe is verified by an automated test against the published npm packages, which tells the agent the output is authoritative rather than illustrative, and that exact file contents are returned.

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?

Two tight sentences front-load the deliverable, then the verification guarantee, then the route semantics. Nothing is redundant; minor awkwardness from the quoted 'vite'/'html' phrasing is negligible.

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 single-param, read-only recipe tool with no output schema, the description covers what is produced (exact file contents), why it is trustworthy (tested against npm packages), and what each route yields. An agent can invoke it correctly without further information.

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?

Schema coverage is 0%, so the description must carry the parameter meaning, and it does: 'vite' is defined as an npm + Vite project using @ortho-earth/globe (marked recommended), and 'html' as a plain page without a bundler. Only the default value handling is left implicit, but the schema supplies default='vite'.

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

Purpose4/5

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

The description names a concrete deliverable — a step-by-step recipe plus exact file contents for putting the Ortho Earth globe in a web page — which is far more specific than the vague name 'get_started'. It does not explicitly contrast itself with siblings like search_docs or view_link, so an agent must infer the boundary.

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 implied rather than stated: this is the scaffolding starting point. The description does give clear selection guidance between the two routes ('vite' recommended, 'html' for no bundler), but says nothing about when to pick this tool over search_docs or list_apps.

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.