Skip to main content
Glama

rtfm

Retrieve Android development documentation for build tools, ADB commands, emulators, UI automation, or cache management to support application building and debugging.

Instructions

Get documentation. Pass category or tool name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoCategory: build, adb, emulator, ui, cache
toolNoTool name for specific docs

Implementation Reference

  • The core handler function for the 'rtfm' tool, which reads and returns documentation files based on the input category or tool name.
    export async function handleRtfmTool(input: RtfmInput): Promise<{ content: string }> {
      if (!input.category && !input.tool) {
        const content = await readFile(join(RTFM_DIR, "index.md"), "utf-8");
        return { content };
      }
    
      if (input.category) {
        try {
          const content = await readFile(join(RTFM_DIR, `${input.category}.md`), "utf-8");
          return { content };
        } catch {
          return { content: `Category '${input.category}' not found. Available: build, adb, emulator, ui, cache` };
        }
      }
    
      const category = TOOL_TO_CATEGORY[input.tool!] || "index";
      try {
        const content = await readFile(join(RTFM_DIR, `${category}.md`), "utf-8");
        const toolSection = extractToolSection(content, input.tool!);
        return { content: toolSection || content };
      } catch {
        return { content: `Tool '${input.tool}' not found.` };
      }
    }
  • Input schema validation for the rtfm tool.
    export const rtfmInputSchema = z.object({
      category: z.string().optional(),
      tool: z.string().optional(),
    });
  • Definition object used to register the 'rtfm' tool in the MCP server.
    export const rtfmToolDefinition = {
      name: "rtfm",
      description: "Get documentation. Pass category or tool name.",
      inputSchema: {
        type: "object",
        properties: {
          category: { type: "string", description: "Category: build, adb, emulator, ui, cache" },
          tool: { type: "string", description: "Tool name for specific docs" },
        },
      },
      annotations: {
        readOnlyHint: true,
        destructiveHint: false,
        idempotentHint: true,
        openWorldHint: false,
      },
    };
Behavior2/5

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

No annotations provided, so description carries full burden. Fails to disclose return format, expected content structure, or confirm read-only nature. 'Get' implies reading but doesn't guarantee no side effects.

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?

Extremely terse at two sentences with no filler. However, given the lack of annotations and output schema, this brevity contributes to underspecification rather than efficient communication.

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

Completeness2/5

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

With no output schema and no annotations, the description should explain what documentation format is returned and how to interpret it. It fails to compensate for missing structured metadata.

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

Parameters3/5

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

Schema has 100% description coverage with clear parameter descriptions. The description adds no semantic meaning beyond the schema, meeting the baseline for high-coverage schemas.

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

Purpose3/5

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

States the tool retrieves documentation, but is vague about what documentation (tool docs, general help, etc.) and doesn't explicitly distinguish from the action-oriented siblings (adb-*, gradle-*, etc.).

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

Usage Guidelines2/5

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

Mentions 'Pass category or tool name' but provides no guidance on when to use category vs tool, whether they are mutually exclusive, or if the tool can be called with neither parameter (both are optional per schema).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/thecombatwombat/replicant-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server