Skip to main content
Glama

BRAINIAC Technical Analysis Indicators

Build a volume profile with POC and value area

technical-analysis_volume-profile
Read-onlyIdempotent

Spread caller-supplied bar volume across equal price bins and return the histogram, point of control, and value area high and low. Price $0.03 USDC. POST /api/v1/technical-analysis/volume-profile. 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": {
      "bars": "<bars>"
    },
    "name": "technical-analysis_volume-profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
barsYesbars, array. Required.
rowsNorows, integer, from 2 to 500. Optional.
tickSizeNotickSize, number. Optional.
valueAreaPctNovalueAreaPct, number, from any to 1. Required.

Output Schema

NameRequiredDescriptionDefault
pocNopoc. Number.
vahNovah. Number.
valNoval. Number.
binsNobins. Array.
paramsNoparams. Object.
warmupNowarmup. Object.
sourcesNosources. Array.
limitationsNolimitations. Array.
totalVolumeNototalVolume. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the annotations, the description discloses critical behavior: the tool costs $0.03 USDC, is exposed via POST at a specific endpoint, and an unpaid call returns x402 payment terms instead of running. That payment and failure-mode context is exactly what an agent needs for a paid API call, and it is consistent with the read-only, idempotent annotations.

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 three compact sentences: computation first, then price, endpoint, and unpaid-call behavior. Every sentence carries functional or operational information, with no wasted preamble.

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?

Given the output schema and annotations, the description covers the core computation and the important paid-access behavior, including what happens when payment is missing. It is nearly complete, though it could say more about how the optional tuning parameters affect the resulting profile.

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 the baseline is 3. The description adds useful meaning by saying the volume is caller-supplied and spread across equal price bins, but it does not explain key optional parameters such as rows, tickSize, or how valueAreaPct controls the value area. The schema's own parameter descriptions are mostly tautological, so the description could have compensated more.

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 names a specific action: spreading caller-supplied bar volume across equal price bins, and it states the concrete outputs: histogram, point of control, and value area high and low. This clearly distinguishes it from sibling indicator tools because it builds a volume profile from supplied bars rather than calculating a standard indicator.

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 only implied: an agent can infer it should call this when it has caller-supplied bars and needs a volume profile. There is no explicit 'use when' guidance, no conditions for choosing this over sibling tools, and no exclusions. Payment and endpoint details are operational context rather than tool-selection guidance.

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