tradingview-mcp-server

list_fields

Read-onlyIdempotent

Discover available fields for filtering and sorting market data. Specify a category and asset type to narrow results for targeted screening and analysis.

Instructions

List available fields for filtering and display. Use this to discover what fields you can filter and sort by.

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

Input Schema

Name	Required	Description	Default
`category`	No	Filter fields by category. If omitted, returns all categories
`asset_type`	No	Type of asset. Default: 'stock'

Output Schema

Name	Required	Description	Default
`fields`	Yes
`category`	Yes
`asset_type`	Yes
`field_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.7.0Aug 19, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "asset_type": {
+      "type": "string"
+    },
+    "category": {
+      "type": "string"
+    },
+    "field_count": {
+      "type": "integer"
+    },
+    "fields": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "asset_type",
+    "category",
+    "field_count",
+    "fields"
+  ],
+  "type": "object"
+}

First observedv0.0.0-devJul 13, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is clear. The description adds that fields are intended for filtering and display, which is useful context, but it does not add much beyond that. No contradiction with annotations.

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?

Two concise sentences with no filler. The purpose and usage are front-loaded, and every word adds value.

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

Completeness5/5

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

Given the simple two-parameter schema with full descriptions, an output schema, and safe annotations, the description fully covers what an agent needs to understand and invoke the tool correctly.

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 both parameters fully documented via descriptions and enums. The tool description adds no additional semantics beyond what the schema provides, so baseline 3 is appropriate.

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 lists available fields for filtering and display, distinguishing it from sibling screening and lookup tools. The verb 'List' and resource 'fields' are specific and unambiguous.

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?

It explicitly says to use this to discover filterable/sortable fields, providing clear when-to-use context. However, it does not mention when not to use or name alternative tools, so it stops short of full guidance.

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

Deploy Server