TradeHub

My trading permissions

get_my_trading_permissions

Read-onlyIdempotent

What this agent may do right now on TradeHub: autonomy level (read, propose = every order needs a person's approval, preauth = executes within limits), allowed venues, symbols and actions, per-trade and daily limits, today's usage, connected venues and whether trading is halted. Use first in every session and after any rejection that mentions your mandate. Not for account balances (use get_my_balances). No inputs. Limits are fractions of equity or USD. Only a person can widen them, on the Web, and widening waits 24 hours. Next: size_position or get_my_positions.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`today`	Yes	orders_today and realized_pnl_today (USD) for this agent, UTC day
`scopes`	Yes	OAuth / API key scopes this caller holds
`mandate`	Yes	This agent's trading permissions (its mandate): level (read / propose / preauth), venues, symbols, actions, max_risk_pct (fraction of equity at stop), max_leverage, max_notional_usd, max_positions, daily_loss_budget_usd, daily_order_limit, expires_at. null on a limit = only the user's global limit
`delegation`	No	Who this agent acts for and where its rights come from
`real_money`	No	For an agent allowed only the sandbox: how it can come to trade real money
`deprecation`	No	Present only while this tool is deprecated: replacement, removal_date, changelog
`trading_halted`	Yes	True after a stop: no new positions until a person resumes on the Web
`venues_connected`	Yes	Venues the user has connected (sandbox is always there)

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedNov 3, 2026
- removedInput schema / title
```
Removed value: -"get_my_trading_permissionsArguments"
```
- addedOutput schema / properties / delegation / additionalProperties
```
Added value: +true
```
- removedOutput schema / properties / delegation / anyOf
```
Removed value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedOutput schema / properties / delegation / default
```
Removed value: -null
```
- removedOutput schema / properties / delegation / title
```
Removed value: -"Delegation"
```
- addedOutput schema / properties / delegation / type
```
Added value: +[
+  "object",
+  "null"
+]
```
- addedOutput schema / properties / deprecation / additionalProperties
```
Added value: +true
```
- removedOutput schema / properties / deprecation / anyOf
```
Removed value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedOutput schema / properties / deprecation / default
```
Removed value: -null
```
- removedOutput schema / properties / deprecation / title
```
Removed value: -"Deprecation"
```
- addedOutput schema / properties / deprecation / type
```
Added value: +[
+  "object",
+  "null"
+]
```
- removedOutput schema / properties / mandate / title
```
Removed value: -"Mandate"
```
- removedOutput schema / properties / real_money / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedOutput schema / properties / real_money / default
```
Removed value: -null
```
- removedOutput schema / properties / real_money / title
```
Removed value: -"Real Money"
```
- addedOutput schema / properties / real_money / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / scopes / title
```
Removed value: -"Scopes"
```
- removedOutput schema / properties / today / title
```
Removed value: -"Today"
```
- removedOutput schema / properties / trading_halted / title
```
Removed value: -"Trading Halted"
```
- removedOutput schema / properties / venues_connected / title
```
Removed value: -"Venues Connected"
```
- removedOutput schema / title
```
Removed value: -"Permissions"
```

Changed1 schema field changedNov 2, 2026

addedOutput schema / properties / real_money

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "For an agent allowed only the sandbox: how it can come to trade real money",
+  "title": "Real Money"
+}

First observedOct 27, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description still adds substantive behavior: the autonomy-tier semantics (read / propose / preauth), that limits are fractions of equity or USD, and that widening limits requires a human on the Web with a 24-hour delay. That last fact is a governance constraint the agent could not infer from any structured field.

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?

Dense but every clause earns its place: capability inventory first, then usage triggers, then exclusions, then semantic notes, then next steps. No filler and no repetition of annotation data.

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

Completeness5/5

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

An output schema exists, so return values are covered elsewhere; the description supplies what structure cannot — interpretation of the autonomy levels and limits, the escalation path for widening, and where to go next. Complete for a zero-parameter read tool in a large sibling set.

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

Parameters4/5

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

The tool takes no inputs and the description says so directly ('No inputs'), which matches the empty schema. With zero parameters there is no semantic gap, though the statement itself is minimal rather than additive — consistent with the baseline for parameterless tools.

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 ('What this agent may do right now on TradeHub') and enumerates the exact contents: autonomy level, allowed venues/symbols/actions, limits, usage, connected venues, halt status. It explicitly distinguishes itself from a sibling by excluding balances and naming get_my_balances.

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

Usage Guidelines5/5

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

Gives explicit when-to-use triggers ('Use first in every session and after any rejection that mentions your mandate'), an explicit when-not ('Not for account balances'), and follow-on alternatives ('Next: size_position or get_my_positions'). Nothing is left to inference about routing.

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

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

Resources

Need Help?