Tldr Pages

Commands

commands

Read-onlyIdempotent

List every command-line utility that has a tldr-pages cheatsheet, filtered to one platform (common, linux, osx, windows, android, sunos, freebsd) and one ISO 639-1 language, read from the tldr-pages index published on GitHub. Returns the command names plus a count. Answers which shell commands tldr documents for a given platform, before fetching a page.

Input Schema

Name	Required	Description	Default
`language`	No
`platform`	No

Output Schema

Name	Required	Description
`count`	Yes	Number of commands returned
`commands`	Yes	List of command names
`language`	Yes	Language code used
`platform`	Yes	Platform filter used

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "language": "en",
+    "platform": "linux"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "commands": {
+      "description": "List of command names",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "count": {
+      "description": "Number of commands returned",
+      "type": "number"
+    },
+    "language": {
+      "description": "Language code used",
+      "type": "string"
+    },
+    "platform": {
+      "description": "Platform filter used",
+      "type": "string"
+    }
+  },
+  "required": [
+    "platform",
+    "language",
+    "count",
+    "commands"
+  ],
+  "type": "object"
+}

First observedMay 18, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive. Description adds the data source (GitHub tldr-pages index), output shape (names + count), and its role as a pre-page lookup. No contradictions.

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 sentences, front-loaded with the core action and filters. The second sentence states output, the third gives workflow context. No filler, though slightly dense.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given an output schema exists, the description needn't detail return types. It covers what the tool does, source, filters, and output count, making it self-contained.

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

Parameters5/5

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

Input schema has no descriptions or enums, but the description compensates by listing valid platform values (common, linux, osx, windows, android, sunos, freebsd) and specifying language as ISO 639-1. This gives agents the needed parameter constraints.

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?

Clearly states it lists command-line utilities from the tldr-pages index, filtered by platform and language, returning names and a count. The phrase 'before fetching a page' distinguishes it from the sibling 'page' tool.

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?

Provides clear context for when to use it: to see which shell commands tldr documents for a platform before fetching a page. It doesn't explicitly name alternatives like 'page' or 'platforms' but implies the workflow.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Tldr Pages tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.