fathom-fyi

set_custom_strategy

Define custom trading strategies with specific conditions to evaluate against market data for financial decision-making.

Instructions

Create a custom trading strategy with your own conditions. Then use evaluate_strategy to test it against current market conditions.

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": {
      "name": "<name>",
      "conditions": "<conditions>"
    },
    "name": "set_custom_strategy"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Name for your strategy
`conditions`	Yes	Array of conditions that must ALL be met

Schema Changelog

Changes observed during successful MCP inspections.

First observedv4.5.1Mar 25, 2026

TDQS

A4.1/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. States 'Create' implying mutation/persistence, and mentions workflow with evaluate_strategy. However, lacks details on idempotency (duplicate names?), return values, or side effects (does it activate immediately?).

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, zero waste. Front-loaded with purpose, second sentence earns its place by providing critical workflow context. No redundancy with structured fields.

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?

Creation tool with no annotations and no output schema. Description provides adequate workflow context (use evaluate_strategy next) but omits what this returns (strategy ID?), persistence behavior, or error conditions. Adequate but gaps remain for a state-mutating operation.

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 has 100% description coverage, establishing baseline 3. Description references 'conditions' generally but adds no syntax details, examples, or format guidance beyond what the schema already provides for the nested field/operator/threshold structure.

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?

Clear specific verb (Create) + resource (custom trading strategy) + scope (with conditions). Explicitly distinguishes from sibling evaluate_strategy by stating this tool creates while that one tests.

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?

Excellent workflow guidance: explicitly directs user to 'use evaluate_strategy to test it against current market conditions' after creation. Clear sequencing between create and evaluation phases.

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