MangroveAI

list_positions

Read-onlyIdempotent

Read positions recorded in MangroveAI for the authenticated user and organization. This does not read platform trading positions.

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

Input Schema

Name	Required	Description
`asset`	No	Asset symbol, e.g. BTC or ETH.
`limit`	No	Maximum results.
`offset`	No	Pagination offset in the result units documented by the tool; zero starts the first page.
`open_only`	No	Leave out positions that have already been closed.
`strategy_id`	No	The strategy's UUID.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 14, 2026
- changedInput schema / properties / limit / default
```
Previous value: -50New value: +25
```
Changed8 schema fields changedNov 5, 2026
- addedInput schema / properties / asset / description
```
Added value: +"Asset symbol, e.g. BTC or ETH."
```
- addedInput schema / properties / limit / default
```
Added value: +50
```
- addedInput schema / properties / limit / description
```
Added value: +"Maximum results."
```
- addedInput schema / properties / offset
```
Added value: +{
+  "default": 0,
+  "description": "Pagination offset in the result units documented by the tool; zero starts the first page.",
+  "type": "integer"
+}
```
- addedInput schema / properties / open_only / default
```
Added value: +true
```
- addedInput schema / properties / open_only / description
```
Added value: +"Leave out positions that have already been closed."
```
- addedInput schema / properties / strategy_id / description
```
Added value: +"The strategy's UUID."
```
- addedInput schema / required
```
Added value: +[]
```
First observedOct 22, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without prose. The description adds real value by disclosing the data boundary (tenant-scoped to the authenticated user and organization, excluding platform trading positions), which annotations cannot express. It says nothing about result volume, ordering, or what a "position" record contains, which is the remaining behavioral gap.

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 compact sentences with the scope stated first and the exclusion second, so nothing is buried and no wording is wasted. It is arguably under-sized rather than over-sized, but every sentence earns its place.

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?

All five parameters are optional and fully documented in the schema, and annotations cover the read-only/idempotent profile, so the short description is nearly sufficient. The one real gap is the absence of an output schema combined with no description of what a returned position contains, which an agent must guess.

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%, with each of the five parameters (asset, limit, offset, open_only, strategy_id) documented inline, so the baseline of 3 applies. The description adds no parameter-level meaning beyond the schema, but nothing is left undocumented either.

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 ("Read") plus the resource ("positions") and scopes it to "the authenticated user and organization," which tells the agent exactly whose positions are returned. It adds a useful negative scope ("This does not read platform trading positions"), but it never names a sibling such as list_trades or list_signals, so differentiation from those list tools is left to inference.

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?

The second sentence functions as a when-not clause by excluding platform trading positions, and the user/organization scoping implies the primary use case. However, it gives no positive guidance on when to pick this over sibling list tools (e.g., list_trades) and states no prerequisites, so usage is only implied.

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

All MangroveAI 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.