Skip to main content
Glama
CHRONOS-AGENT

CHRONOS-AGENT

chronos_query_hotspots

Identify the top N performance bottlenecks and hot-path functions by querying a 4D knowledge graph, using live telemetry or PageRank + loop fallback.

Instructions

Query the 4D Knowledge Graph for the top N performance bottlenecks and hot-path functions (using live telemetry or PageRank + O(N^2) loop fallback).

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_query_hotspots"
  }
}

Input Schema

NameRequiredDescriptionDefault
top_nNoNumber of hotspots to return (default: 10)
filterNoFilter type (default: all)all
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.3/5.0
Behavior3/5

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

With no annotations, the description carries the whole burden; it does disclose a meaningful behavioral trait by revealing that results may come from 'live telemetry or PageRank + O(N^2) loop fallback', implying variable latency and degraded accuracy when telemetry is absent. It does not say what triggers the fallback, that the operation is read-only, or what the response shape looks like.

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?

A single front-loaded sentence: the verb and resource come first, and the method parenthetical follows as secondary detail. Nothing is redundant — even the fallback note earns its place by explaining result provenance.

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?

All three optional parameters are schema-documented, so the description needn't restate them, and there is no output schema to explain. However, for a tool with a non-trivial ranking/fallback pipeline and truncation semantics, it should mention the telemetry prerequisite and what happens when max_answer_chars truncates.

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%, so top_n, filter, and max_answer_chars are already fully documented with defaults and the enum's meaning. The description adds only the 'top N' framing, which the schema already conveys, so baseline 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?

States a specific verb ('Query') and resource ('4D Knowledge Graph') plus the exact yield ('top N performance bottlenecks and hot-path functions'), which is concrete enough to separate it from generic graph queries like chronos_query_graph. It never names a sibling explicitly, so differentiation relies on inference from the resource phrase.

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 explicit when-to-use or when-not-to-use guidance, no prerequisites (e.g., whether telemetry must be hydrated first via chronos_hydrate_telemetry), and no named alternative for adjacency, callers, or general graph traversal. Usage is only inferable from the performance-oriented wording of the purpose.

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