Skip to main content
Glama
CHRONOS-AGENT

CHRONOS-AGENT

chronos_get_architecture

Get a high-level architecture overview of a codebase: community clusters, language breakdown, entry points, top PageRank hubs, and hidden O(N^2) algorithmic hotspots, scoped to a directory path.

Instructions

Get a high-level architecture overview: community clusters (Label Propagation + Cohesion score), language breakdown, entry points, top PageRank hubs, and hidden O(N^2) algorithmic hotspots.

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

Input Schema

NameRequiredDescriptionDefault
pathNoOptional directory prefix to scope architecture analysis
auto_indexNoAutomatically scan and incrementally index workspace files (default: true)
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?

No annotations are supplied, so the description carries the full burden. It does disclose the analytical machinery behind each output section (Label Propagation, Cohesion score, PageRank, O(N^2) detection), which is real behavioral context, but it never states cost/latency for what is clearly an expensive whole-repo analysis, nor that the default auto-indexing writes to the workspace index, nor that results are read-only and non-destructive.

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 puts the high-level framing first and then the payload list; there is no filler. It is dense with jargon (Cohesion score, O(N^2) hotspots) that a cold agent may need to interpret, but nothing is wasted.

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?

With no output schema, the description usefully enumerates the returned sections, which is exactly what the agent needs to decide whether this call answers its question. The residual gap is operational (cost, indexing side effect, result size), which matters for a zero-annotation, workspace-wide analysis tool.

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 (path, auto_index, max_answer_chars) are already documented in the schema at the baseline level. The description adds no further meaning about scoping semantics, indexing side effects, or what truncation does to the overview sections, so the baseline 3 applies.

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 ("Get a high-level architecture overview") and enumerates the concrete sections returned: community clusters with Label Propagation + Cohesion, language breakdown, entry points, PageRank hubs, and O(N^2) hotspots. That enumeration makes it distinguishable from narrower siblings like chronos_query_hotspots or chronos_query_graph without naming them explicitly.

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: "high-level" and "overview" suggest this is the orientation/starting-point call before drilling into specific symbols or hotspots, but no when-to-use, when-not-to-use, or named alternative is stated. The agent must infer that chronos_analyze_file or chronos_query_hotspots are the narrower follow-ups.

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