Skip to main content
Glama

get_performance_hotspots

Retrieve the top performance hotspots in a selected subsystem, sorted by time spent. Use expansion ids to drill down into specific methods or call trees.

Instructions

Retrieve a sorted list of top performance hotspots. Returns a JSON object containing an array of hotspots with timing data and expansion ids. Use expand_performance_hotspot to drill down.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
subsystemYesThe subsystem (as provided by check_status, for example cpu or jdbc) to analyze.
wallTimeNoOptional, used for the cpu subsystem only: If true, time spent in all thread states will be used, otherwise only the runnable state is used. Defaults to false.
packageFilterNoOptional comma-separated package filter to focus on classes of interest.
viewNoThe view type: either 'hotspots' (the default) to focus on the methods/statements that most time is spent in or 'call_tree' to get a structural view of the time spent.
Behavior3/5

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

Describes the return type (JSON with array of hotspots, timing data, expansion ids) but lacks details on side effects, data freshness, or access requirements. With no annotations, it provides basic but not comprehensive behavioral context.

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 sentences, front-loaded with purpose and return, no unnecessary words. Efficient and clear.

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

Completeness3/5

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

Covers basic purpose and return structure, but lacks information on error handling, pagination, or limits. With 4 parameters and no output schema, could be more thorough.

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?

The description does not add meaning beyond the input schema, which has 100% coverage. Baseline of 3 is appropriate as schema already documents parameters fully.

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?

Clearly states the tool retrieves a sorted list of performance hotspots, specifying verb and resource. Differentiates from sibling expand_performance_hotspot which has a different purpose.

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 a clear alternative (expand_performance_hotspot) for drilling down, indicating when this tool is appropriate. However, does not explicitly state when not to use it or provide exclusions.

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/ej-technologies/jprofiler-mcp'

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