Skip to main content
Glama
daniel3303

Equibles

by daniel3303
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

CBOE Put/Call Ratios

GetPutCallRatios
Read-only

Gauge market sentiment by analyzing CBOE put/call ratios. Retrieve data for Equity, Index, or Vix to determine if market bias is bearish (high ratio) or bullish (low ratio).

Instructions

Get CBOE put/call ratio data showing market sentiment. Available types: Total (all exchange), Equity, Index, Vix, Etp. High ratios (>1.0) indicate bearish sentiment; low ratios (<0.7) indicate bullish sentiment. Volumes are contract counts. Data available from November 2006 to present (the Vix type from October 2019); pre-2013 history is sampled roughly weekly rather than daily.

Input Schema

NameRequiredDescriptionDefault
typeNoRatio type: Total, Equity, Index, Vix, Etp (default: Equity)Equity
endDateNoEnd date in YYYY-MM-DD format (defaults to latest available)
startDateNoStart date in YYYY-MM-DD format (defaults to 3 months ago)
maxResultsNoMaximum number of records to return (default: 60, max: 500). When the range holds more rows the newest are kept; rows are always listed oldest to newest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true, consistent with the data retrieval nature. Description adds behavioral context: sampling frequency for pre-2013 data and available types (Total, Equity, etc.). 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is concise with three sentences, front-loaded with purpose and key details. Slightly verbose with repeated 'available types' but still efficient.

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?

No output schema, but description sufficiently explains return values (ratio data, volumes). Covers data history, sampling, and interpretation. Missing explicit note about required permissions or response format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and description adds value by explaining the meaning of ratio values for the 'type' parameter and order for 'maxResults'. Could include more detail about date format validation.

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 clearly states it gets CBOE put/call ratio data for market sentiment, with specific verb 'get' and resource 'CBOE put/call ratio data'. It distinguishes from siblings by focusing on this unique sentiment indicator.

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?

The description explains interpretation of high/low ratios and data availability periods, providing context for use. However, it does not explicitly mention when to use this tool over similar sentiment tools like GetShortVolume or GetVixHistory.

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