Skip to main content
Glama
Sign In
durable-mcp

durable-mcp

by cshah26
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_spread_analysis

Analyze spread trading PnL breakdown by path, book, or book+path to evaluate win rate, Calmar ratio, and best/worst days.

Instructions

Get detailed breakdown of spread trading PnL by path (source→sink), book, or book+path. Shows win rate, Calmar ratio, best/worst days per path or book. Use this when asked about specific paths, books, source/sink pairs, or route-level performance.

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": {
      "date_from": "<date_from>",
      "date_to": "<date_to>"
    },
    "name": "get_spread_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupNoPortfolio group name to filter by (leave blank to list available groups)
date_toYesEnd date in YYYY-MM-DD format
breakdownNoBreakdown dimension: path (source→sink), book, or book+pathpath
date_fromYesStart date in YYYY-MM-DD format

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It implies read-only ('Get detailed breakdown') and mentions specific metrics (win rate, Calmar ratio), but does not disclose potential side effects, auth needs, or rate limits. Adequate but could be more comprehensive.

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: first states purpose and outputs, second gives usage guidance. Very concise, front-loaded, and no wasted words.

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?

For a tool with 4 params, no output schema, and no annotations, the description covers purpose, usage, and key metrics shown. It lacks output format details but compensates by listing metrics. Slightly incomplete regarding error conditions or permissions, but sufficient given context.

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 coverage is 100%, so baseline is 3. The description reinforces breakdown options by explaining 'path (source→sink)', but adds little beyond schema descriptions for other parameters. It does not add new parameter-specific meaning.

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?

The description starts with 'Get detailed breakdown of spread trading PnL by path, book, or book+path', providing a specific verb and resource. It clearly distinguishes from sibling tools like get_flow_analysis by focusing on spread trading PnL breakdowns.

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

Usage Guidelines4/5

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

Explicitly states 'Use this when asked about specific paths, books, source/sink pairs, or route-level performance', providing clear context for when to use. While it doesn't explicitly list when not to use, the sibling list implies alternatives.

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

Deploy Server

Other Tools