Skip to main content
Glama
LuciferForge

agent-safety-mcp

by LuciferForge
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

trace_summary

Summarize trace session details including step count, errors, and timing for monitoring and debugging agent safety operations.

Instructions

Get a summary of the current trace session — step count, errors, timing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/agent_safety_mcp/server.py:331-335 (handler)
    The implementation of the 'trace_summary' MCP tool. It retrieves the tracer and returns its summary.
    @mcp.tool()
def trace_summary() -> dict:
    """Get a summary of the current trace session — step count, errors, timing."""
    tracer = _get_tracer()
    return tracer.summary()

Tool Definition Quality

B3.4/5.0
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 what data is returned (step count, errors, timing) but omits critical safety/disposition details: whether calling this clears the trace, if it requires an active session, or idempotency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, front-loaded with the action and resource. The em-dash efficiently lists summary contents without wasted words. Every clause earns its place.

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?

Adequate for a zero-parameter tool but incomplete given no output schema exists. The description hints at return content (step count, errors, timing) but doesn't clarify error conditions (e.g., behavior if no trace is active) or output structure.

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

Parameters4/5

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

Input schema has zero parameters. Per rubric, zero-parameter tools baseline at 4. The description requires no parameter clarification.

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?

Clear verb ('Get') and resource ('summary of the current trace session'). The enumerated fields (step count, errors, timing) help distinguish it from sibling trace tools like trace_start or trace_step, though 'Get' is slightly generic.

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 explicit guidance on when to use this versus trace_start, trace_step, or trace_save. The description implies a reporting function but doesn't state prerequisites (e.g., 'use after starting a trace') or workflow position.

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