Skip to main content
Glama
Sign In

Thales

by report.thales
OverviewDiscussionsAdmin

sleeve_record

Full public record for one sleeve: stats, indexed performance curve (100 = inception), drawdown series, and the complete submitted-order log. All figures are SIMULATED paper trading.

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": {
      "sleeve": "<sleeve>"
    },
    "name": "sleeve_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
sleeveYesWhich sleeve to fetch
includeNostats = summary only; curve (alias: equity) = + indexed performance/drawdown series; trades = + full order log; all = everythingstats

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / include / description
      Previous value: -"stats = summary only; equity = + daily equity/drawdown series; trades = + full order log; all = everything"New value: +"stats = summary only; curve (alias: equity) = + indexed performance/drawdown series; trades = + full order log; all = everything"
    • changedInput schema / properties / include / enum
      Previous value: -[
-  "stats",
-  "equity",
-  "trades",
-  "all"
-]New value: +[
+  "stats",
+  "curve",
+  "equity",
+  "trades",
+  "all"
+]
  2. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses that figures are simulated paper trading, which is useful context, and implies a public read operation. However, it doesn't mention rate limits, error behavior, or explicit safety guarantees, leaving gaps.

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?

Two sentences, front-loaded with the tool's purpose and contents, followed by a critical simulation warning. Every word earns its place with no fluff or redundancy.

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?

Given the simple parameter set and no output schema, the description adequately covers the tool's return contents and simulation context. It could elaborate on the return format or pagination, but for a list/record fetch, it is reasonably complete.

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?

Schema coverage is 100%, providing baseline 3. The description adds value by explaining the indexed performance curve (100 = inception) and enumerating the include options, which goes beyond the schema's terse descriptions.

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?

The description clearly states the tool returns the full public record for one sleeve, listing specific components (stats, indexed performance curve, drawdown series, order log). It does not explicitly differentiate from siblings, but the resource and action are clear.

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 description implies usage (fetch a sleeve's record) but provides no explicit when-to-use guidance or alternatives among siblings. It doesn't state exclusions or conditions, so only implied context exists.

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

All Thales toolsInspect
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