Skip to main content
Glama
fiale-plus

tradingview-mcp-server

by fiale-plus
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

screen_forex

Read-onlyIdempotent

Screen forex pairs based on technical indicators and filters, returning matching instruments.

Instructions

Screen forex pairs based on technical criteria. Returns forex pairs matching the specified filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to return (1-200). Default: 20
columnsNoOptional: specific columns to include in results. If not provided, uses default columns.
filtersNoArray of filter conditions to apply
sort_byNoField to sort results by. Default: 'volume'
sort_orderNoSort order. Default: 'desc'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pairsYes
metadataYes
total_countYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changedv0.7.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / filters / items / additionalProperties
      Added value: +false
    • changedInput schema / properties / filters / items / properties / value / description
      Previous value: -"Value to compare against. Not required for 'empty' and 'not_empty' operators. Use number, string, or [min, max] array for in_range. For above_percent/below_percent, use [field_name, percent_number] e.g. ['SMA200', 10]."New value: +"Value to compare against. Empty and not_empty omit value. above_percent and below_percent use [field, percent]. has and has_none_of use a non-empty string array."
    • addedInput schema / properties / filters / items / properties / value / oneOf
      Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "string"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "items": {
+      "type": "number"
+    },
+    "maxItems": 2,
+    "minItems": 2,
+    "type": "array"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "minItems": 1,
+    "type": "array"
+  },
+  {
+    "maxItems": 2,
+    "minItems": 2,
+    "prefixItems": [
+      {
+        "type": "string"
+      },
+      {
+        "type": "number"
+      }
+    ],
+    "type": "array"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "metadata": {
+      "additionalProperties": false,
+      "properties": {
+        "cache_hit": {
+          "type": "boolean"
+        },
+        "missing_symbols": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "requested_count": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "retrieved_at": {
+          "format": "date-time",
+          "type": "string"
+        },
+        "returned_count": {
+          "minimum": 0,
+          "type": "integer"
+        },
+        "source": {
+          "type": "string"
+        },
+        "unavailable_symbols": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "retrieved_at",
+        "source",
+        "cache_hit",
+        "requested_count",
+        "returned_count",
+        "missing_symbols"
+      ],
+      "type": "object"
+    },
+    "pairs": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_count": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "total_count",
+    "pairs",
+    "metadata"
+  ],
+  "type": "object"
+}
  2. First observedv0.0.0-dev

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description's 'Returns forex pairs' aligns with a read-only operation. The description adds minimal behavioral context beyond the annotations, such as the fact that it filters based on criteria, but does not disclose any edge cases like default limits or sorting behavior. No contradiction.

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 extremely concise at two sentences with no filler. It is front-loaded with the primary action and result. However, its brevity comes at the cost of missing usage context, so it earns a 4 rather than 5.

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?

This is a complex screening tool with a rich filter schema, multiple operators, and examples in the schema. The description provides only a high-level one-liner and does not orient the agent to the available filter fields, operators, or general workflow. Despite the output schema and annotations, the description is not sufficient for a tool of this complexity.

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%, with detailed parameter descriptions for limit, columns, filters, sort_by, and sort_order. The description adds no extra parameter semantics, but the schema carries the full burden. Baseline 3 is appropriate as the schema is self-explanatory.

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 identifies the tool as a screener for forex pairs using technical criteria. The verb 'screen' and the resource 'forex pairs' make the purpose unambiguous, and it differentiates from sibling tools that screen other asset classes. However, 'technical criteria' is generic and could be more specific about the indicators involved.

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 the tool is used for screening forex pairs, but it does not explicitly state when to use this tool versus alternatives like screen_stocks or screen_crypto. No exclusions or comparison to siblings are provided, leaving the agent to infer the asset class from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fiale-plus/tradingview-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server