Skip to main content
Glama

startup

Breaks down the last launch into timed phases—process init, video pipeline, window shown, launch file opening, React mounting, and control port—to pinpoint where a slow start occurred.

Instructions

The last launch's startup timeline, phase by phase, in milliseconds from process start — process init, video pipeline, window shown, the launch file opening, React mounting, the control port. Use it to say where a slow start went rather than that it was slow.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses scope (only the last launch, not history), the measurement basis (milliseconds from process start), and the phase breakdown, which implicitly confirms this is a passive read. It does not say what is returned when no launch has been recorded, nor whether phase values are cumulative offsets or per-phase durations — meaningful ambiguities for a timing tool.

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 what is returned and followed by the decision guidance. The em-dash phase list is dense but every element is informative; there is no 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?

There is no output schema, so the description must sketch the return value — and it does, by naming each phase and the unit. For a zero-parameter diagnostic that is nearly sufficient; only the empty/no-launch case and the cumulative-vs-per-phase interpretation of the numbers are left unstated.

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 takes no parameters, so there is nothing for the description to disambiguate; the baseline applies. The description correctly spends its words on the result shape instead of inventing argument semantics.

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?

Names a specific resource — the startup timeline of the last launch — and enumerates the phases it contains (process init, video pipeline, window shown, launch file opening, React mounting, control port). An agent can immediately tell this is a zero-argument retrieval of launch timing data, with no overlap with siblings like describe_frame or dev_snapshot.

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?

The closing sentence gives explicit intent guidance: use it to localize where a slow start occurred rather than just confirming slowness. That is a real use-case statement, but there is no when-not condition and no named alternative for related diagnostics, so it stops short of full routing guidance.

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