Skip to main content
Glama

OHLCV gap checker

submit_ohlcv_gap_checker
Idempotent

Check OHLCV bars for high/low inversions, out-of-range prices, zero volume and time gaps. Before using a price series, to catch corrupt bars. Do not choose this when missing sessions must be fetched from a data provider. Example requests: Check this OHLCV data for bad bars. | Are there gaps in this price series? | Clean this market data file.

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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_ohlcv_gap_checker"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already state readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the semantics of what is being checked, but omits the most consequential behaviour: this submits a priced job that requires a quote_id and human/agent authorization. Because that is partly recoverable from the schema's quote_id and accepted_price descriptions, it is a gap rather than a contradiction.

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 tight sentences up front (what it checks, when to use it, when not to) with the example requests placed last as optional routing aids. Slight redundancy between the check list and the 'bad bars / gaps' examples, but nothing that wastes real space.

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?

An output schema exists, so return-value explanation is unnecessary, and the check semantics are complete. However, for a non-read-only job submission with a required authorization parameter and a stored-quote check, the description never tells the agent that a job must be quoted and then authorized — a material omission given the sibling tools submit_job and preflight_job.

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 75%, close to the high-coverage baseline, and the nested ohlcv property already documents CSV-with-header and the 1 MB limit. The description adds nothing about any of the four parameters — notably it never mentions that a quote_id and authorized_by are required to run it — so it neither compensates for the uncovered quarter nor enriches the documented ones.

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 names a specific verb and resource ('Check OHLCV bars') and enumerates the exact defect classes it detects: high/low inversions, out-of-range prices, zero volume, and time gaps. That is far more specific than siblings like submit_csv_quality_report or submit_time_series_anomaly_config, though it never explicitly contrasts itself with those neighbours.

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?

It gives a clear precondition ('Before using a price series, to catch corrupt bars') and an explicit exclusion ('Do not choose this when missing sessions must be fetched from a data provider'), plus three example phrasings that map natural requests to the tool. It stops short of naming a concrete alternative capability to use instead of the excluded case.

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