Skip to main content
Glama

Trader desk strategies

get_desk_strategies
Read-only

Strategies sold by verified trader desks on OwlChart: title, desk, track record, price. With a strategy pass (Bearer owlpass_ bought at /api/desk-strategies/{id}/buy) and the strategy id, returns the written rules of the strategy and its alert bundle, as data. Data and analysis only.

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

Input Schema

NameRequiredDescriptionDefault
deskNoOptional desk slug
strategyNoA strategy id you hold a pass for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful context beyond that: an authentication prerequisite (Bearer owlpass_ purchased from a specific endpoint) and the fact that the deep response is returned as data rather than executed. The 'Data and analysis only' disclaimer clarifies that outputs are informational, not actionable signals.

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 sentences, front-loaded with the returned fields and followed by the gated mode, with no filler. Minor drag from parenthetical clutter (the full buy URL inline) and the trailing 'Data and analysis only' fragment, but nothing is redundant.

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 no output schema, the description does a fair job sketching both return shapes (summary fields vs. rules plus alert bundle), and it covers the auth requirement. It stops short of describing pagination, result limits, or what happens when a pass is missing or expired, which matters for an open-world, credentialed tool.

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%, so the baseline is 3, but the description goes further by explaining that 'strategy' requires a held pass and that supplying it unlocks the rules and alert-bundle payload, which the schema alone does not convey. It also confirms the desk parameter acts as an optional filter. This adds real conditional meaning on top of the field 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 names the specific resource (strategies sold by verified trader desks on OwlChart) and enumerates the returned fields (title, desk, track record, price), so the agent knows exactly what it is fetching. It also distinguishes the two modes: a listing mode versus a pass-gated mode that returns written rules and an alert bundle. It loses a point only because the leading phrase lacks an explicit verb and the mode switch is buried in the second sentence.

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 through the parameter semantics: omit everything to browse desks, supply 'desk' to filter, supply 'strategy' plus a pass to retrieve rules. The prerequisite for the second mode is stated clearly (a pass bought at /api/desk-strategies/{id}/buy). However, there is no explicit when-to-use or when-not-to-use guidance relative to siblings such as get_marketplace_alerts, leaving the agent to infer which tool covers alerts.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources