android-dev-mcp

get_session_hygiene

Learn when to use /clear vs /compact in Claude Code sessions: get context window limits, autocompact thresholds, and CLAUDE.md hygiene rules to prevent context overflow.

Instructions

Returns /clear vs /compact rules, context window facts, autocompact buffer thresholds, and CLAUDE.md hygiene.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1Aug 2, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. The verb 'Returns' implies a read-only operation, but no additional behavioral context is given (e.g., whether it reads from a config, runs calculations, or connects to a service). This is minimally transparent but not misleading.

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 one compact, well-structured sentence, front-loading the action ('Returns') and then enumerating the specific content categories. Every word earns its place with no repetition or filler.

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?

The tool is simple with no parameters and no output schema. The description enumerates all the major content areas the tool returns, which is likely complete for the intended purpose. It slightly lacks clarity on the output format, but that is not critical given the systematic listing of information types.

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 the description need not explain parameter meanings. The schema is empty, and the description adds no parameter details, which is acceptable at the baseline of 4 for parameterless tools.

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 returns session hygiene related information, listing specific items: /clear vs /compact rules, context window facts, autocompact buffer thresholds, and CLAUDE.md hygiene. This specific verb and resource list distinguishes it from sibling tools like get_full_context or get_project_structure.

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

Usage Guidelines1/5

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

There is no guidance on when to use this tool versus alternatives. Given the large sibling set with similar get_* naming, the description should indicate situations where session hygiene details are needed, but it does not.

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