Skip to main content
Glama
CHRONOS-AGENT

CHRONOS-AGENT

chronos_hydrate_telemetry

Hydrate runtime telemetry into the ChronosGraph from offline profiler artifacts such as V8 .cpuprofile, Speedscope, folded stacks, or OTLP JSON to enrich code-graph analysis with execution data.

Instructions

Hydrate the 4th Dimension (runtime telemetry) of the ChronosGraph from an offline profiler artifact (V8 .cpuprofile JSON, Speedscope/py-spy JSON, Folded Stack Flamegraph text, or OpenTelemetry OTLP trace JSON).

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

Input Schema

NameRequiredDescriptionDefault
profile_pathNoPath to the offline profile file (.cpuprofile, .speedscope.json, .folded, .otlp.json)
profile_contentNoOptional inline profile content string (alternative to profile_path)
max_answer_charsNoOptional maximum character budget for the response (default: 24000; <= 0 disables truncation)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does add real behavioral information by enumerating the four supported profile formats and framing the source as an 'offline' artifact, but it never states that this mutates graph state, whether repeated hydration overwrites prior telemetry, how large profiles are handled, or what the call returns. The mutation semantics of the primary operation are left entirely implicit.

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?

A single front-loaded sentence that identifies the operation first and then the supported inputs, with no filler or repetition. The nested parentheticals make it dense, but nothing is wasted.

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?

For an ingestion/mutation tool with zero annotations, no output schema, and a schema where all three parameters are optional, the description should clarify source selection (path vs inline content) and the effect on existing telemetry. Neither is covered, leaving an agent able to call it but unsure how to invoke it correctly or what it does to prior data.

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 description coverage is 100%, so all three parameters are already documented with types, defaults, and file-extension hints, which sets the baseline at 3. The description adds only the format names that loosely map to those extensions. Critically, it does not explain that neither profile_path nor profile_content is required and that at least one must be supplied, which is the main semantic gap.

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 names a concrete verb ('Hydrate') and a concrete resource ('4th Dimension (runtime telemetry) of the ChronosGraph'), and it enumerates the accepted artifact types (V8 .cpuprofile, Speedscope/py-spy, Folded Stack Flamegraph, OTLP trace JSON). An agent can tell this is a profiler-artifact ingestion tool rather than a query or edit tool. It stops short of naming any sibling to distinguish itself from, so it lands at 4 rather than 5.

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?

There is no when-to-use or when-not-to-use guidance: nothing says this must be called before runtime-aware queries, whether re-hydration replaces or merges existing telemetry, or which of profile_path/profile_content should be preferred. The only implied guidance is the list of accepted file formats. No alternative tool or precondition is referenced.

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