Skip to main content
Glama

profiler-commit-query

Query React commit data to investigate render performance by component, time range, commit index, or cascade tree after profiling has stopped.

Instructions

Query React commit data for iterative investigation of render performance. Requires react-profiler-stop to have been called first. Modes:

  • by_component: All commits where a specific component rendered, with causes and durations.

  • by_time_range: What happened in a specific time window.

  • by_index: Full detail dump of a single commit (all components, props changed, parent cascade).

  • cascade_tree: Parent-child cascade tree for a commit showing who triggered whom. Use when drilling into specific components or time windows after react-profiler-analyze. Returns a markdown table or tree of commit data matching the requested mode. Fails if react-profiler-stop has not been called or no commit data is stored.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeYesQuery mode: by_component (commits for a component), by_time_range (commits in a window), by_index (full detail for one commit), cascade_tree (parent-child cascade for a commit)
portNoMetro server port
top_nNoMax results to return (default 20)
device_idYesDevice logicalDeviceId from debugger-connect (iOS simulator UDID or Android logicalDeviceId).
commit_indexNoCommit index for by_index and cascade_tree modes
time_range_msNoTime range filter for by_time_range mode
component_nameNoComponent name for by_component mode
Behavior3/5

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

Discloses failure conditions (stop not called, no data) and return type (markdown table or tree). No annotations provided, so description carries full burden. Does not address side effects, auth, or rate limits, but as a query tool these may be minimal.

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?

Concise with logical flow: purpose, prerequisites, modes, usage note, return type, failure condition. No superfluous sentences; front-loaded with core purpose.

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?

Covers prerequisites, failure conditions, return type, and mode descriptions. Without output schema, the description adequately outlines what to expect. Lacks some details on parameter interactions but schema fills gaps.

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?

All seven parameters are described in the schema (100% coverage). The description adds high-level mode explanations but adds little beyond schema details for individual parameters, staying at baseline for full coverage.

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?

Clearly states it queries React commit data for render performance investigation, listing four specific modes with brief descriptions. Differentiates from sibling profiler tools by mentioning its use after react-profiler-analyze, though not exhaustively.

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

Usage Guidelines3/5

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

Explicitly requires react-profiler-stop to have been called and warns of failure if not. Advises using after react-profiler-analyze. Lacks explicit exclusion of other modes or alternatives among the many sibling profiler tools.

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/software-mansion/argent'

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