Skip to main content
Glama
LuciferForge

agent-safety-mcp

by LuciferForge

trace_start

Start a new trace session to create signed audit trails for AI agent safety monitoring, tracking interactions and outputs for security analysis.

Instructions

Start a new trace session for an AI agent.

Args: agent: Agent name (used in filenames). trace_dir: Directory to save trace files. model: Optional model name to attach as metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agentNodefault
trace_dirNo./traces
modelNo

Implementation Reference

  • The `trace_start` tool implementation, which initializes a new `Tracer` instance with an agent name, directory, and optional metadata.
    @mcp.tool()
    def trace_start(
        agent: str = "default",
        trace_dir: str = "./traces",
        model: str = "",
    ) -> dict:
        """Start a new trace session for an AI agent.
    
        Args:
            agent: Agent name (used in filenames).
            trace_dir: Directory to save trace files.
            model: Optional model name to attach as metadata.
        """
        global _tracer
        meta = {}
        if model:
            meta["model"] = model
        _tracer = Tracer(agent=agent, trace_dir=trace_dir, meta=meta if meta else None)
        return {
            "status": "started",
            "agent": agent,
            "trace_dir": trace_dir,
        }
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses file system side effects ('Directory to save trace files'), indicating this is a write operation. However, it omits critical behavioral details such as whether existing traces are overwritten, required directory permissions, return value format, or error handling behavior.

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 description is appropriately sized with a clear purpose statement followed by a structured Args block. Every sentence earns its place. The docstring-style Args format is readable, though slightly informal; it efficiently packs necessary parameter details without redundancy.

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 three-parameter tool with no output schema and no annotations, the description adequately covers parameter semantics but leaves gaps regarding the return value (success indication, session ID, or handle) and error conditions (invalid paths, permission failures). It mentions side effects but doesn't fully characterize the session lifecycle.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Given 0% schema description coverage, the description fully compensates by documenting all three parameters in the Args section: 'agent' explains filename usage, 'trace_dir' clarifies the save location purpose, and 'model' notes the metadata attachment. This provides essential semantic meaning beyond the bare types in 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 clearly states the verb 'Start' and resource 'trace session for an AI agent', providing immediate understanding. However, it does not explicitly differentiate from siblings like trace_step, trace_save, or trace_summary, which could help the agent understand the workflow sequence.

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?

No guidance is provided on when to use this tool versus alternatives, nor are prerequisites mentioned (e.g., whether to check for existing traces first). The description lacks 'when-not' conditions or sequencing guidance relative to the other trace-related sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LuciferForge/agent-safety-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server