Skip to main content
Glama
CHRONOS-AGENT

CHRONOS-AGENT

chronos_get_snippet

Retrieve verbatim source code for any function or class along with its callers, callees, covering tests, and complexity metrics for fast code understanding.

Instructions

Read the verbatim source code (start_line..=end_line) of a function/class from disk along with its callers, callees, covering tests, PageRank, and AST complexity metrics.

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": {
      "symbol_name": "<symbol_name>"
    },
    "name": "chronos_get_snippet"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_pathNoOptional file path filter to disambiguate same-name symbols
symbol_nameYesFunction, method, class name, or 'Class/method' name_path to retrieve
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.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. 'Read' implies a non-mutating operation and the description usefully enumerates returned content (callers, callees, tests, PageRank, AST complexity), but it omits permissions, missing-symbol behavior, and ambiguity handling.

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 definition is a single front-loaded sentence with little wasted wording. It is dense, and the unexplained start_line..=end_line notation slightly reduces clarity, but it remains compact.

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 adequately identifies the main returned artifacts: source code plus callers, callees, tests, PageRank, and AST complexity. It could do more to describe result structure, truncation behavior, or ambiguous-symbol handling, but the essential retrieval contract is present.

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 the schema already documents symbol_name, file_path, and max_answer_chars. The description adds no real parameter guidance beyond the schema; the start_line..=end_line notation does not correspond to any declared parameter and may even confuse line-range usage.

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 states a specific verb and resource: read verbatim source code of a function/class from disk, plus related analytics. It is clear what the tool retrieves, but it does not explicitly distinguish itself from sibling retrieval/graph tools such as chronos_explore or chronos_query_graph.

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?

The description gives no explicit when-to-use or when-not-to-use guidance, and it names no alternatives. Usage is only implied by the retrieval framing, leaving the agent to infer when this is preferable to sibling tools.

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