Skip to main content
Glama
CHRONOS-AGENT

CHRONOS-AGENT

chronos_analyze_file

Parses source files to extract AST symbols, call edges, cross-language HTTP routes, test links, and complexity metrics, then inserts them into the 4D Knowledge Graph.

Instructions

Parse a source file (.ts, .tsx, .js, .py, .rs, .go, .c, .cpp, .java) with CHRONOS's polyglot AST engine and insert all symbols, call edges, cross-language HTTP routes, test edges, and loop/complexity metrics into the 4D Knowledge Graph.

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": {
      "file_path": "<file_path>"
    },
    "name": "chronos_analyze_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathYesAbsolute or workspace-relative path to the source file to analyze
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.7/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 burden. It does disclose the meaningful side effect set (symbols, call edges, cross-language HTTP routes, test edges, loop/complexity metrics get written), but says nothing about idempotency, whether existing graph entries are overwritten or merged, cost on large files, or permission requirements.

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 dense sentence that front-loads the action and language scope before the write targets. No filler, no redundancy with the title, and nothing an agent must skip past to find the operative clause.

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 mutation-style ingestion tool with no annotations and no output schema, the description covers the write footprint well but leaves return values and repeat-invocation behavior unaddressed. An agent knows what to send and what gets stored, but not what it receives back or whether re-running is safe.

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% and both parameters are documented in the schema, including the file_path semantics and the max_answer_chars truncation default. The description adds no additional meaning about path resolution edge cases or response-budget behavior, so the baseline 3 applies.

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?

States a concrete verb+resource pair ('Parse a source file ... insert all symbols, call edges ... into the 4D Knowledge Graph') and enumerates the supported languages and artifact types. An agent can distinguish this ingestion tool from read-oriented siblings like chronos_query_graph or chronos_search_graph without inspecting schemas.

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 only implied: the tool ingests a single file into the graph, so it presumably precedes querying or blast-radius analysis. There is no explicit statement of when to choose this over chronos_explore or chronos_query_graph, nor any when-not condition such as skipping already-indexed files.

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