Skip to main content
Glama

Current facts about Ortho Earth

get_facts
Read-onlyIdempotent

Latest version and release date, npm packages, licenses, and how many official MapLibre GL JS and CesiumJS examples run unchanged on Ortho Earth. Rebuilt on every deploy of www.ortho-earth.com. Call this before stating a version number or a compatibility figure.

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_facts"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false and closed-world scope, so safety is covered. The description adds one genuinely new behavioral fact: the data is regenerated on every deploy of www.ortho-earth.com, which tells the agent the values are deploy-fresh rather than cached. It says nothing further about latency, size, or failure modes.

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?

Three short sentences, front-loaded with the payload contents, then the freshness note, then the usage trigger. Every sentence contributes and nothing is padded.

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?

There is no output schema, so the enumeration of returned facts carries that burden, and it does so reasonably. For a zero-parameter read tool this is close to enough; only the shape or size of the returned payload is left implicit.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to carry; the baseline applies. The description correctly implies a no-argument, lookup-style call by never referencing inputs.

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 enumerates concrete content: latest version and release date, npm packages, licenses, and counts of official MapLibre GL JS and CesiumJS examples that run unchanged. That is a specific resource, not a restatement of the name. It does not explicitly distinguish itself from the sibling check_compat, whose name suggests an overlapping compatibility role.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Call this before stating a version number or a compatibility figure" is an explicit, actionable trigger condition. It stops short of naming when-not cases or pointing at alternatives such as check_compat, but the when-to-use guidance is clear.

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.