Skip to main content
Glama
CHRONOS-AGENT

CHRONOS-AGENT

chronos_generate_agents_md

Synthesize live context rules, skills, and MCP configs from a knowledge graph for AI coding CLIs/IDEs; optionally write files and scaffold native configs.

Instructions

Synthesize live, data-driven context rules, skills, and MCP configs from the 5D Knowledge Graph (AGENTS.md, CLAUDE.md, GEMINI.md, .agents/skills/chronos-agent/SKILL.md, .cursor/rules/chronos-5d.mdc) for OpenAI Codex CLI, Google Antigravity, Claude Code, OpenCode, Cursor, Windsurf, Copilot, and Cline.

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

Input Schema

NameRequiredDescriptionDefault
targetNoTarget AI CLI/IDE ecosystem: codex | antigravity | claude | opencode | cursor | windsurf | copilot | cline | all (default: 'codex')codex
auto_indexNoAutomatically scan and incrementally index workspace files first (default: true)
with_hooksNoIf true (with write_to_disk=true), also scaffolds <20ms lifecycle hook configs (.agents/hooks.json, .claude/settings.json)
output_pathNoOptional relative workspace path override when writing a single context file
project_nameNoOptional project title override for the synthesized header
write_to_diskNoIf true, writes the synthesized file(s) directly into the workspace (default: false)
max_answer_charsNoOptional maximum character budget for the response (default: 24000; <= 0 disables truncation)
scaffold_configsNoIf true (with write_to_disk=true), also scaffolds native MCP configs, skills, and slash commands for the target client

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 supplied, so the description must carry the behavioral load; it does reveal the key fact that writes are opt-in via write_to_disk and that default behavior is likely returning content rather than mutating the workspace. It does not disclose overwrite semantics for existing context files, permission requirements, indexing cost, or what the response contains.

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 dense sentence that front-loads the action and enumerates artifacts and targets, with no filler. The long parenthetical file list and client roster make it slightly hard to scan but each item is substantive.

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?

For a generator tool with 0 required params, full schema coverage, and no output schema, the description conveys the core action and the write-vs-return distinction well enough to call it correctly. It stops short on return shape and side effects on pre-existing files, which would be needed for a fully safe invocation.

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 eight parameters are already documented in the schema; the description adds no parameter-level meaning beyond it. Baseline 3 applies, though it does confirm the artifact-to-target mapping implicitly through the enum list.

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 ('Synthesize') and resource ('context rules, skills, and MCP configs from the 5D Knowledge Graph') plus the concrete artifacts and target clients it produces. The scope is very clear; sibling differentiation is only implicit, since no other chronos_* tool is named as the alternative for graph queries.

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 names targets and artifacts but never says when an agent should call this versus chronos_query_graph, chronos_get_architecture, or chronos_explore, nor when not to use it. There is no prerequisite guidance (e.g., whether indexing must precede it) despite auto_index existing.

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