Skip to main content
Glama

arthas_classloader

Inspect Java classloader hierarchy by listing all classloaders, showing tree view, or finding classes matching a pattern for real-time diagnostics.

Instructions

Show classloader hierarchy and info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
allNoShow all classes
listNoList all classloaders
treeNoShow classloader tree
timeoutNoTimeout in ms
classPatternNoClass pattern
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It only states 'show', implying read-only, but does not mention any side effects, permissions, or limitations. It lacks depth for safe agent invocation.

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?

The single sentence is concise and front-loaded. It earns its place by stating the core function, but additional structure (e.g., parameter hints) would improve usability.

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?

Given 5 parameters and no output schema, the description is insufficient. It does not explain the relationship between parameters or what 'info' includes, leaving an AI agent underinformed.

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 coverage is 100% with descriptions for all 5 parameters. The description adds no extra meaning beyond the schema, which is acceptable per guidelines. Baseline score 3 is appropriate.

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

Purpose4/5

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

The description clearly states the tool shows 'classloader hierarchy and info', which is a specific verb and resource. However, it does not differentiate from siblings like arthas_jvm or arthas_thread which also show info, but the classloader focus is distinctive.

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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or when not to use it.

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/HeavenC/arthas-mcp'

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