Skip to main content
Glama
Sign In
tradinview-mcp

tradinview-mcp

by Ham12-3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Verify provider

verify_provider

Check that a market data provider returns valid quote and OHLCV data for a given symbol and interval.

Instructions

Perform a quote and OHLCV smoke check against a configured provider.

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": "verify_provider"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerNo
symbolNoBTCUSDT
intervalNo1h

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations exist, so the description must disclose behavior. It mentions 'smoke check' but does not explain whether it modifies data, what it returns, or how failures are handled. Minimal behavioral information.

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?

The description is a single concise sentence with no wasted words. However, it is so brief that it sacrifices clarity and completeness.

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 no output schema, no annotations, and three parameters with zero description coverage, the description is insufficient for an agent to reliably invoke the tool. Missing expected return format and error conditions.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not clarify parameter meaning beyond their names. For instance, 'provider' is not described, and 'symbol' default is mentioned in schema but not in description. Little added value.

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 performs a smoke check using quote and OHLCV data, distinguishing it from sibling tools like get_quote or get_ohlcv which merely fetch data. However, it could be more explicit about what a 'smoke check' entails.

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 provided on when to use this tool versus siblings such as get_quote or get_ohlcv. Missing context about prerequisites or conditions.

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