Skip to main content
Glama
Sign In
ib-async-mcp

ib-async-mcp

by atomcp-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_head_timestamp

Retrieve the earliest available historical data timestamp for a financial contract, given contract type and symbol.

Instructions

Get earliest available historical data timestamp.

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": {
      "contract_type": "<contract_type>",
      "symbol": "<symbol>"
    },
    "name": "get_head_timestamp"
  }
}

Input Schema

NameRequiredDescriptionDefault
contract_typeYes
symbolYes
exchangeNoSMART
currencyNoUSD
what_to_showNoTRADES

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2.4/5.0
Behavior2/5

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

The description only says 'get earliest available historical data timestamp' without disclosing behavioral traits such as whether it requires a connection, if it's read-only, or what it returns. With no annotations provided, the description carries the full burden but fails to provide adequate behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is a single sentence, achieving conciseness. However, it lacks structure and important details, so it does not earn its place optimally.

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

Completeness2/5

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

Given that the tool has 5 parameters, 2 required, no output schema, and no parameter descriptions, the description is insufficient. It does not explain the return value, prerequisites, or how the parameters affect the result.

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

Parameters1/5

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

The input schema has 0% schema description coverage, meaning no descriptions are provided for any of the 5 parameters. The tool description also does not add any meaning to the parameters, leaving the agent to guess their roles and formats.

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 clearly states the tool gets the earliest available historical data timestamp. It uses a specific verb and resource, distinguishing it from sibling tools like get_historical_data or get_current_time.

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?

No guidance is given on when to use this tool versus alternatives. There is no mention of context or exclusions, making it unclear for an agent to decide when to invoke it.

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