Skip to main content
Glama
CHRONOS-AGENT

CHRONOS-AGENT

chronos_contract_status

Retrieve and clear pending semantic contract violation alerts detected since the last check, so coding agents can enforce pre-tool execution gates before making changes.

Instructions

Drain the Semantic Contract Broker's Pre-Tool Execution Gate. Returns any pending contract violation alerts detected since the last call.

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

Input Schema

NameRequiredDescriptionDefault
watch_dirNoDirectory to index for contract changes (optional)
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
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 disclosure burden. 'Drain' and 'since the last call' hint that alerts are consumed and will not reappear, but the description never states this explicitly, nor does it say whether reading the gate has side effects on blocked operations or whether alerts persist after being returned. For an unannotated tool with consumption semantics, that is a material gap.

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?

Two short sentences, verb-first, with no filler. The jargon density slightly hurts immediate comprehension but the structure is front-loaded and efficient.

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 tool with no annotations, no output schema, and a consuming-drain behavior, the description should say what an alert record contains and confirm whether returned alerts are cleared. It covers the surface purpose but leaves the operationally important semantics unspecified.

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 coverage is 100%, so watch_dir and max_answer_chars are already documented in structured form, and the description adds nothing about them. Baseline 3 is appropriate since the schema does the work.

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 action (drain) and a specific resource (pending contract violation alerts from the Pre-Tool Execution Gate), so an agent can tell what comes back. The framing is heavy with internal jargon ('Semantic Contract Broker', 'Pre-Tool Execution Gate'), and it does not distinguish itself from contract-adjacent siblings like chronos_mutation_gate, which keeps it from a 5.

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?

The phrase 'detected since the last call' implies a polling/cursor pattern and gives some context for when to invoke it, but there is no explicit when-to-use versus when-to-skip guidance and no mention of sibling tools. Usage is left to inference.

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