Skip to main content
Glama
Sign In
QuantOracle

QuantOracle

by QuantOracledev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

indicators_fibonacci-retracement

Read-onlyIdempotent

Compute Fibonacci retracement levels (23.6% to 78.6%) and extension levels (127.2% to 261.8%) from a swing high and swing low price.

Instructions

Fibonacci retracement and extension levels.

Use when computing Fibonacci retracement and extension levels. Provide a high price and low price. Returns: retracement levels (23.6%, 38.2%, 50%, 61.8%, 78.6%) and extension levels (127.2%, 161.8%, 261.8%).

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": {
      "swing_high": "<swing_high>",
      "swing_low": "<swing_low>"
    },
    "name": "indicators_fibonacci-retracement"
  }
}

Input Schema

NameRequiredDescriptionDefault
directionNoTrend direction for level calculationup
swing_lowYesSwing low price
swing_highYesSwing high price

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idlempotentHint=true, destructiveHint=false. The description adds value by listing the exact retracement and extension levels returned, which is behavioral detail beyond the annotations. No contradictions.

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?

The description is extremely concise: two sentences plus a list of levels. It is front-loaded with the purpose and has no fluff. Every sentence earns its place.

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?

Despite no output schema, the description enumerates the exact retracement and extension levels returned. For a simple calculation tool with well-known inputs, this provides sufficient context for an agent to use the tool correctly.

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 description coverage is 100%: all three parameters (swing_high, swing_low, direction) are described in the schema. The description's mention of 'Provide a high price and low price' adds no new semantics beyond the schema, so a baseline of 3 is appropriate.

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?

Description clearly states it computes Fibonacci retracement and extension levels, specifies exact levels returned, and identifies required inputs (high and low prices). It distinguishes itself from sibling tools like indicators_bollinger-bands or indicators_atr by being specific to Fibonacci calculations.

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 says 'Use when computing Fibonacci retracement and extension levels.' It does not provide exclusions or alternatives, but the context is clear enough for an agent to decide when to invoke this tool versus other technical indicators.

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