Skip to main content
Glama
Nice-Wolf-Studio

DataBento MCP Server

by Nice-Wolf-Studio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

metadata_get_cost

Calculate the USD cost of a historical data query before downloading. Specify dataset, symbols, and date range to estimate fees.

Instructions

Calculate the cost in USD for a historical data query before downloading

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
datasetYesDataset code (e.g., GLBX.MDP3)
symbolsNoComma-separated list of symbols or single symbol
schemaNoSchema name (default: trades)
startYesInclusive start date/time (YYYY-MM-DD or ISO 8601)
endNoOptional exclusive end date/time (YYYY-MM-DD or ISO 8601)
modeNoQuery mode (default: historical-streaming)
stype_inNoInput symbology type (e.g., raw_symbol, continuous)
stype_outNoOutput symbology type (e.g., instrument_id, raw_symbol)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided, so description must cover behavioral traits. It only states a calculation, without disclosing whether it requires authentication, rate limits, or what the response format is. Minimal transparency.

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 a single efficient sentence that immediately conveys the purpose, with no wasted words.

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?

With 8 parameters and no output schema, the description provides no information about the output format, units (beyond USD), or how cost is computed. This is insufficient for an agent to understand the tool's full behavior.

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 baseline 3 is appropriate. The description does not add any extra meaning beyond the schema's parameter descriptions, which are comprehensive.

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 the tool calculates cost in USD for a historical data query before downloading, using a specific verb and resource, and distinguishes it from sibling tools like batch_download or get_historical_bars.

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 use for cost estimation before downloading, but lacks explicit guidance on when not to use or alternatives. Among siblings, batch_submit_job might involve similar cost, but no comparison is given.

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