Skip to main content
Glama
CHRONOS-AGENT

CHRONOS-AGENT

chronos_query_graph

Run read-only Cypher queries against the embedded KuzuDB 4D knowledge graph to inspect code nodes, metrics, and relationships such as CALLS, CONTAINS, TESTS, and IMPORTS.

Instructions

Execute a Read-Only Cypher query directly against the embedded KuzuDB 4D Knowledge Graph. Every ChronosNode has properties: id, name, qualified_name, kind, file, start_line, end_line, start_byte, end_byte, cognitive_load, cyclomatic, fan_in, fan_out, param_count, sloc, loop_count, loop_depth, transitive_loop_depth, linear_scan_in_loop, alloc_in_loop, is_recursive, is_hydrated, exec_time_p50, exec_time_p99, invocation_count, cpu_percent, is_hot_path, is_bottleneck. Relationship tables: CALLS, CONTAINS, TESTS, IMPORTS, CO_CHANGES_WITH.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "chronos_query_graph"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesRead-only Cypher query (e.g. 'MATCH (f:ChronosNode) WHERE f.transitive_loop_depth >= 2 RETURN f.name, f.file, f.transitive_loop_depth')
max_rowsNoMaximum rows to return (default: 500, ceiling: 100000)
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

A3.5/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 and does well to declare the operation read-only and to enumerate the graph model. It omits what happens if a write clause is attempted, whether there are timeouts or cost limits beyond the schema's row/char ceilings, and what the result 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and read-only constraint are front-loaded in the first sentence, followed by the graph model. The long comma-separated property list is dense but earns its place for query authoring; it could be grouped or bulleted for faster scanning, but no sentence is filler.

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?

For a raw-query tool with no output schema and no annotations, the graph model disclosure is substantial, but return-value behavior is left implicit: whether results are objects or arrays, how columns are keyed, and what truncation under max_answer_chars looks like. The truncation semantics live only in the schema, so the description does not fully close the gap.

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?

Schema coverage is already 100%, establishing a baseline of 3. The description adds real value by publishing every ChronosNode property and relationship table, which directly informs how to construct the required query parameter rather than leaving the agent to guess at the graph model.

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 and resource: executing read-only Cypher against the embedded KuzuDB 4D Knowledge Graph, which clearly separates it from prebuilt-query siblings like chronos_query_hotspots or chronos_search_graph. It stops short of naming a sibling or saying explicitly that raw Cypher is the differentiator, so the distinction is inferable rather than stated.

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?

Usage is implied by the read-only constraint and the worked Cypher example, which shows the intended pattern. There is no explicit when-to-use guidance versus the prebuilt query tools, and no statement of when this raw-query escape hatch should be preferred or avoided.

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