FIXSIM

List inbound execution reports

fixsim_list_executions_in

Read-onlyIdempotent

Execution reports the user's system sent INTO FIXSIM on a session (when FIXSIM is the order sender and the user's system is the executing side). Optionally filter by ExecID (tag 17).

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": {
      "instance": "<instance>",
      "session": "<session>"
    },
    "name": "fixsim_list_executions_in"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max rows to return, newest first (default 25, max 200)
`apiKey`	No
`execId`	No	Optional ExecID (tag 17) filter
`session`	Yes
`instance`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 12, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds meaningful domain behavior: which counterparty originates these reports and on which side FIXSIM sits, which matters for interpreting results. It does not discuss volume/pagination behavior beyond what the schema states.

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?

A single front-loaded sentence plus one short optional-filter clause. Every phrase conveys domain meaning and there is no filler.

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?

The direction-of-flow explanation is the essential context for this tool and is present, and annotations cover the read/idempotent profile. However, with 5 parameters, two of them required and undocumented, and no output schema, the definition leaves an agent guessing about instance/session semantics.

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 coverage is only 40%, so the description must carry more weight than it does. It repeats the ExecID (tag 17) filter already documented in the schema and says nothing about the two required parameters, instance and session, nor about apiKey.

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+resource (list execution reports) and disambiguates by direction of flow: reports the user's system sent INTO FIXSIM. This contrasts cleanly with the outbound sibling fixsim_list_executions_out even without naming it.

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?

Specifies the scenario that selects this tool (FIXSIM is the order sender, the user's system is the executing side) and notes the optional ExecID filter. It does not explicitly name the alternative tool to use when the direction is reversed, but the context is clear.

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

All FIXSIM tools Inspect

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.