Skip to main content
Glama
CHRONOS-AGENT

CHRONOS-AGENT

chronos_search_graph

Search a 4D knowledge graph by BM25-ranked identifiers, regex patterns, node degree, and nested-loop complexity to find code symbols and routes.

Instructions

Search the 4D Knowledge Graph using BM25 ranked identifier tokenization (splits camelCase/snake_case), regex pattern matching, degree filtering, and nested-loop complexity filtering.

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

Input Schema

NameRequiredDescriptionDefault
kindNoFilter by node kind: Function | Class | ApiRoute | TestCase
limitNoMaximum results to return (default: 50)
queryNoNatural-language or keyword query ranked by BM25 + structural boost + PageRank
offsetNoPagination offset (default: 0)
min_degreeNoMinimum total degree (fan_in + fan_out)
file_patternNoSubstring or regex filter on file path
name_patternNoRegex pattern to match symbol name or qualified_name
min_loop_depthNoMinimum interprocedural nested loop depth (transitive_loop_depth)
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

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It conveys that results are BM25-ranked with identifier splitting, but says nothing about result shape, truncation via max_answer_chars, pagination behavior, or cost, which matters for a nine-parameter search over a graph.

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?

It is a single front-loaded sentence with no padding, but it is a dense run-on that spends words on internals such as camelCase/snake_case splitting rather than on operational guidance an agent needs before calling it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With nine parameters, no annotations, and no output schema, the description should compensate for what the structured fields do not say. It does not explain response truncation, pagination limits, ranking implications, or results format, leaving the agent underinformed about how to invoke this search well.

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 input schema already explains every parameter, including degree, loop-depth, and pattern filters. The description only restates those mechanisms in compressed form and adds no syntax, format, or interaction detail beyond the schema.

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 names a specific verb (Search) and resource (4D Knowledge Graph) and enumerates the mechanisms it applies (BM25 tokenization, regex matching, degree and loop-depth filtering). It never contrasts itself with close siblings like chronos_query_graph or chronos_explore, so an agent cannot distinguish the two from the text alone.

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 statement of when to use this search versus the other graph-querying siblings, nor any prerequisite or exclusion. The clause listing filters hints at capability but gives no situational guidance such as 'use this for regex patterns on symbol names' or 'use chronos_query_graph for natural structure traversal'.

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