remus-mcp

Overview Schema Source Related Servers Discussions Admin

get_traces

Retrieve traces for a given object ID in a project, filtering by incoming, outgoing, or both directions to analyze dependencies.

Instructions

Get traces for oid

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "oid": "<oid>"
    },
    "name": "get_traces"
  }
}

Input Schema

Name	Required	Description	Default
`oid`	Yes
`direction`	No
`project_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 1, 2026

TDQS

C2.7/5.0

Behavior2/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure. 'Get' implies a read operation, but the description does not reveal whether direction defaults to 'both', whether results are paginated, what happens when no traces exist, or what the return structure is. The optional direction parameter's default behavior is left undisclosed.

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 extremely concise, consisting of a single front-loaded sentence with no filler. While it is arguably too terse for full comprehension, as a concise summary it is structurally efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With three parameters, no output schema, and no annotations, this description is incomplete. It fails to explain the meaning of traces, the role of project_id, the direction parameter, or the response shape. An agent would likely need to inspect other tools or code to call this correctly.

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

Parameters2/5

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

Schema description coverage is 0%, and the description adds little meaning beyond parameter names. It gives 'oid' slight contextual meaning (traces for that oid), but it does not clarify project_id, direction semantics, or how incoming/outgoing/both affect the result.

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 gives a specific verb and resource: 'Get traces for oid'. It identifies the scope of the operation (traces belonging to an oid), which is stronger than a tautology. However, it does not clarify what 'traces' are or differentiate from sibling tools like trace_matrix or trace_add.

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 provides no guidance on when to use this tool versus alternatives such as trace_matrix, trace_add, or trace_remove. There is no mention of exclusions, prerequisites, or context like whether project_id must refer to an open project.

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