Skip to main content
Glama

BRAINIAC Options Analytics

Parse or build OCC option symbols

options-analytics_occ-symbol-parse
Read-onlyIdempotent

Parse or build OCC Options Symbology Initiative 21-character option symbols, validating the calendar date and flagging roots that look adjusted. Price $0.02 USDC. POST /api/v1/options-analytics/occ-symbol-parse. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "options-analytics_occ-symbol-parse"
  }
}

Input Schema

NameRequiredDescriptionDefault
buildNobuild, array. Required.
parseNoparse, array. Required.

Output Schema

NameRequiredDescriptionDefault
builtNobuilt. Array.
modelNomodel. String.
parsedNoparsed. Array.
sourcesNosources. Array.
inputsUsedNoinputsUsed. Object.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the bar is lower; the description still adds real context beyond them: a $0.02 USDC cost, the POST endpoint, and the x402 payment gating that causes an unpaid call to return payment terms without executing. It also discloses validation and adjusted-root flagging, which are behavioral traits not visible in the annotations.

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?

Dense and front-loaded: capability first, then validation traits, then cost, then endpoint, then payment gating. Every sentence carries information, though the raw endpoint path is arguably redundant with the tool name and costs one clause.

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?

An output schema exists, so return-value documentation is not required, and the description covers cost, payment failure behavior, validation, and root flagging. The one material omission is the semantics of supplying both optional arrays (or neither), which matters for correct invocation of this otherwise simple two-parameter tool.

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 parameter meaning is already carried by the schema and the baseline is 3. The description adds only peripheral meaning (the 21-character format constraint relevant to 'parse' and calendar-date validation relevant to 'expiry'), and does not explain the interaction or mutual exclusivity of the two optional array parameters.

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?

States a specific verb pair (parse/build) and a precise resource (OCC Options Symbology Initiative 21-character option symbols), plus scope-defining behaviors: calendar-date validation and adjusted-root flagging. Nothing in the sibling list overlaps this symbol-conversion utility, so an agent can recognize the tool's purpose without opening the schema.

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?

The description implies two operating modes via 'Parse or build' but never says which mode to pick, whether both arrays may be supplied in one call, or what happens if both are omitted. There is no explicit when-to-use or when-not-to-use guidance relative to the other options-analytics siblings.

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