Tldr Pages

Platforms

platforms

Read-onlyIdempotent

List the platform keys present across the tldr-pages cheatsheet collection (common, linux, osx, windows, android, sunos, freebsd), derived from the tldr-pages index published on GitHub. Returns the sorted set of platform values that the page, commands, and search tools in this pack accept. Answers which platform value to pass when looking up a tldr command cheatsheet.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`platforms`	Yes	Sorted list of supported platforms

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples
```
Added value: +[
+  {}
+]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "platforms": {
+      "description": "Sorted list of supported platforms",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "platforms"
+  ],
+  "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 declare the tool read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond this: it is 'derived from the tldr-pages index published on GitHub' and 'Returns the sorted set,' disclosing the source and ordering behavior.

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?

The description is three sentences, each earning its place: (1) states the primary list operation and enumerates the platforms, (2) explains the returned sorted set and its relation to other tools, (3) gives a practical usage example. No filler or redundancy.

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?

For a simple no-parameter tool with an output schema, the description is complete. It covers what the tool does, the source of the data, the return behavior (sorted set), and how to use it when invoking other commands. Nothing essential is missing.

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 has zero parameters, so baseline is 4. The description doesn't need to explain parameters, and the input schema fully covers the empty parameter set. The description reinforces the purpose rather than adding parameter-specific semantics.

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 clearly states the tool's function: 'List the platform keys present across the tldr-pages cheatsheet collection' and 'Returns the sorted set of platform values that the page, commands, and search tools in this pack accept.' It uses a specific verb and resource, and distinguishes itself from sibling tools by positioning as the source for platform values used by other tools.

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?

The description provides clear context for when to use the tool: 'Answers which platform value to pass when looking up a tldr command cheatsheet.' While it doesn't explicitly name alternatives or exclusions, the context is sufficient to guide selection among siblings.

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

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.