Skip to main content
Glama

Apps and demos built with Ortho Earth

list_apps
Read-onlyIdempotent

The apps and demos on www.ortho-earth.com, each with its link and a one-line description. Useful for showing what the engine can do.

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": "list_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds value beyond that by disclosing the shape of each returned item (link plus one-line description) and the practical purpose of the list. It stops short of saying whether the catalog is complete or static, which keeps it from a 5.

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

Conciseness5/5

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

Two short sentences with zero filler. The resource and its contents are front-loaded, and the use case follows immediately, so an agent gets the essential facts in the first clause.

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?

With no parameters, no nested objects, and no output schema, the description carries the return-value burden and does so by describing each item as a link plus a one-line description. Only minor omissions remain, such as whether the list is exhaustive or ordered, which are unlikely to affect 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?

The tool takes zero parameters and the schema is correspondingly empty, so there is nothing for the description to disambiguate. Baseline 4 applies; no parameter-level gaps exist.

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 specific resource — the apps and demos on www.ortho-earth.com — and states what each entry contains (a link and a one-line description). The listing verb is only implied by the tool name rather than the description text, and no sibling is named for contrast, but the resource is unambiguous enough to distinguish it from check_compat, get_facts, or search_docs.

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?

"Useful for showing what the engine can do" implies a use case (demonstrating capabilities, pointing users at examples), which is more than nothing. However, there is no explicit when-to-use statement, no when-not to use it, and no routing to alternatives such as get_started or get_facts for someone seeking introductory material.

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.