FIXSIM

List securities

fixsim_list_securities

Read-onlyIdempotent

Securities (symbol, last price, CUSIP, ISIN) configured on an instance. FIXSIM prices fills from these.

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>"
    },
    "name": "fixsim_list_securities"
  }
}

Input Schema

Name	Required	Description	Default
`apiKey`	No
`instance`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 12, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so safety profile is covered. The description adds behavioral context that securities are 'configured on an instance' and that FIXSIM prices fills from these, which is useful domain context, but does not address pagination, permissions, or return format.

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?

Two short sentences with no wasted words, front-loaded with what the tool lists. Efficient and easy to parse.

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?

With only two parameters, no output schema, and annotations covering read-only behavior, the description is adequate for basic invocation. However, it lacks guidance on the required instance parameter and any return-shape expectations, leaving moderate gaps.

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%, so the description must compensate for undocumented parameters. It mentions the instance implicitly ('configured on an instance') but does not explain the instance parameter's meaning, format, or how to obtain it, and does not mention apiKey at all.

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?

States a specific verb (List) and resource (securities) with the attributes it returns (symbol, last price, CUSIP, ISIN). It does not differentiate from sibling list tools like the various list_orders/executions/instances, but the resource is distinct enough to be identifiable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied by the resource description but there is no explicit when-to-use guidance or naming of alternatives among the many sibling list tools. An agent can infer context (retrieving configured securities) but is not told under which conditions this tool is preferred.

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.