Skip to main content
Glama
Sign In
replicant-mcp

replicant-mcp

by thecombatwombat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

rtfm

Read-onlyIdempotent

Retrieve Android development documentation by specifying a category or tool name. Covers build, adb, emulator, UI, cache, and index topics.

Instructions

Get documentation. Pass category ('build'|'adb'|'emulator'|'ui'|'cache'|'index') or tool (tool name like 'ui-query').

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

Input Schema

NameRequiredDescriptionDefault
categoryNoCategory: build, adb, emulator, ui, cache, index
toolNoTool name (e.g., 'ui-query') for tool-specific docs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.6.7
    • changedInput schema / properties / category / description
      Previous value: -"Category: build, adb, emulator, ui, cache"New value: +"Category: build, adb, emulator, ui, cache, index"
    • changedInput schema / properties / tool / description
      Previous value: -"Tool name for specific docs"New value: +"Tool name (e.g., 'ui-query') for tool-specific docs"
  2. Changed1 schema field changedv1.0.1
    • changedInput schema / properties / category / description
      Previous value: -"Category: build, adb, emulator, ui"New value: +"Category: build, adb, emulator, ui, cache"
  3. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, making safety clear. Description adds minimal behavioral info beyond the query options, so score is average.

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 concise sentences with no wasted words, easy to parse.

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?

Explains input options well but lacks detail on output format; however, for a documentation tool this is acceptable given complexity is low.

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; description adds example values but does not significantly expand meaning beyond schema defaults.

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 it retrieves documentation, listing specific categories and tool names, differentiating it from sibling tools that are actual operations.

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 explicit instructions on passing either category or tool, but does not explicitly state when not to use this tool versus alternatives; context is clear enough though.

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

Deploy Server

Other Tools