Skip to main content
Glama

BRAINIAC Technical Analysis Indicators

Compute classic, Fibonacci, Woodie and Camarilla pivots

technical-analysis_pivot-points
Read-onlyIdempotent

Compute floor, Fibonacci, Woodie and Camarilla pivot levels from the prior period's high, low and close. Price $0.02 USDC. POST /api/v1/technical-analysis/pivot-points. An unpaid call returns the x402 payment terms and does not run.

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": {
      "high": "<high>",
      "low": "<low>",
      "close": "<close>"
    },
    "name": "technical-analysis_pivot-points"
  }
}

Input Schema

NameRequiredDescriptionDefault
lowYeslow, number. Required.
highYeshigh, number. Required.
openNoopen, number. Optional.
closeYesclose, number. Required.
methodsNomethods, array. Required.

Output Schema

NameRequiredDescriptionDefault
paramsNoparams. Object.
warmupNowarmup. Object.
woodieNowoodie. Object.
classicNoclassic. Object.
sourcesNosources. Array.
camarillaNocamarilla. Object.
fibonacciNofibonacci. Object.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, openWorld), the description adds two genuinely useful traits: the $0.02 USDC price and the x402 payment gate where an unpaid call returns payment terms without executing. That is real operational context not present in the structured fields. It does not, however, describe the response shape or how the four method families differ in output, leaving notable behavioral gaps for a paid call.

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?

Three short sentences, front-loaded with the action and resource, followed by cost and payment behavior. No filler or repetition. The bare endpoint string ('POST /api/v1/technical-analysis/pivot-points') is the only near-boilerplate element, though it is plausibly useful for error diagnosis.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and the description covers the remaining essentials: what is computed, from which inputs, at what cost, and what happens when payment is missing. For a stateless calculation endpoint with full schema coverage, nothing required to invoke it correctly is absent.

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%, so all five parameters are already documented, establishing a baseline of 3. The description contributes one piece of added meaning by specifying that high/low/close belong to the 'prior period', which clarifies the correct data window. It says nothing about the optional `open` parameter or the `methods` filter, both of which materially change the output.

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 opens with a specific verb ('Compute') and an enumerated resource ('floor, Fibonacci, Woodie and Camarilla pivot levels'), and names the inputs those levels derive from. An agent can tell this is a multi-method pivot calculator rather than a general indicator tool. It stops short of differentiating itself from the sibling technical-analysis_fibonacci-levels, which overlaps on the Fibonacci method.

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

Usage Guidelines2/5

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

The only contextual condition given is that levels come from the 'prior period's high, low and close', which is an input precondition rather than usage guidance. Nothing states when to pick this over fibonacci-levels or support-resistance, and there are no exclusions or worked scenarios. The agent must infer routing from the sibling names alone.

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