Skip to main content
Glama
Sign In
Adversarial REA

Adversarial REA

by Cultistsid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

inspect_flow_fixture

Reproduce an in-memory flow within a bounded .flow.json fixture to inspect behavior without treating it as native evidence.

Instructions

Reproduce in-memory flow in a bounded .flow.json fixture only; not native evidence

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": {
      "target_path": "<target_path>"
    },
    "name": "inspect_flow_fixture"
  }
}

Input Schema

NameRequiredDescriptionDefault
target_pathYesPath to a declarative .flow.json fixture

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

With no annotations, the description carries full burden, and it does disclose two real traits: the operation is "bounded" (limited scope) and its output is "not native evidence" (lower fidelity). However, it says nothing about read-only behavior, what gets produced, or failure modes for a malformed fixture.

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

Conciseness3/5

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

It is a single compact clause with no filler and the key caveat front-loaded, which is good. But the brevity crosses into under-specification for a tool with no annotations and no output schema, so the size is not truly appropriate to the complexity.

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?

No annotations, no output schema, and no explanation of what the reproduction yields or how it differs from native evidence. For a tool whose whole purpose is a bounded simulation, the agent is left guessing at the return value and the limits of the fixture.

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?

Only one parameter exists and schema coverage is 100%, with target_path already documented as a path to a declarative .flow.json fixture. The description reinforces the fixture file type but adds no syntax, path resolution, or format details beyond the schema. Baseline 3 applies.

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

Purpose3/5

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

It states a verb ("Reproduce") and a resource ("in-memory flow") scoped to a .flow.json fixture, but the phrasing is jargon-dense and never explains what an in-memory flow is or how this relates to sibling analysis tools like trace_calls or analyze_binary. An agent gets a rough sense of purpose but cannot confidently distinguish it from the other inspection tools.

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 word "only" plus "not native evidence" implies a scope boundary (fixture-based simulation rather than ground-truth native analysis), but no alternative tool is named and no condition for choosing this over trace_calls or analyze_binary is given. The agent must infer when this is the right call.

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

Deploy Server

Other Tools