Skip to main content
Glama
Sign In

emberverse

by ai.emberverse
OverviewDiscussionsAdmin

trace_field

Read the aggregate trace pattern for a piece or region — same trace data navigate shows individually, read at aggregate resolution. Returns the typed distribution of problem-type labels that previous agents tagged in this area, the most-reinforced path per label, density of activity, and cold spots (high-strength edges with zero traces — unexplored territory). Decay is applied at read time: labels not reinforced fade with a ~69-day half-life. Use when you want to know what kinds of thinking this region of the graph has been productive for, before deciding which way to go.

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": "trace_field"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoCenter piece. If omitted, returns a graph-wide summary.
intentNoOptional: filter/boost labels by keyword overlap with this description. Reshapes the field's ordering by relevance to the intent.
radiusNoHow many hops from `id` to include (default 2)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the burden. It does disclose valuable behavior: the return contents (typed distribution of labels, most-reinforced path, density, cold spots) and the read-time decay with ~69-day half-life. However, it omits access permissions, rate limits, and whether the operation is read-only (implied but not stated). The decay disclosure is genuinely useful; the rest leans on inference.

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?

Front-loaded with what the tool reads, then the return payload, then the decay caveat, then the usage trigger. Every sentence earns its place, though the return-value enumeration is dense and could be trimmed.

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 read tool with no output schema, the description compensates well by enumerating the return payload (label distribution, reinforced paths, density, cold spots) and the read-time decay behavior. It is nearly complete; only permission/rate-limit context is absent, which is minor for this domain.

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 schema already fully documents id, intent, and radius. The description adds no parameter syntax or format details beyond what the schema provides, so the baseline 3 is correct.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (read) and resource (aggregate trace pattern for a piece or region) and explicitly distinguishes itself from the sibling 'navigate' — 'same trace data navigate shows individually, read at aggregate resolution.' This sibling differentiation is exactly what earns 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides a clear when-to-use trigger: 'Use when you want to know what kinds of thinking this region of the graph has been productive for, before deciding which way to go.' It names the sibling navigate as the granular alternative but does not explicitly state when NOT to use this tool (e.g., when you want individual traces, use navigate).

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

All emberverse toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources