@scom82/topvisor-mcp

topvisor_get_summary_chart

Retrieve position distribution over time for a project and single region, returning dated chart series for rendering.

Instructions

Get chart data showing position distribution over time for a project and single region. Returns dates array and seriesByProjectsId for chart rendering.

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": {
      "project_id": "<project_id>",
      "region_index": "<region_index>"
    },
    "name": "topvisor_get_summary_chart"
  }
}

Input Schema

Name	Required	Description
`project_id`	Yes
`region_index`	Yes	Single region index (from topvisor_list_regions)
`date1`	No	YYYY-MM-DD start date (use with date2)
`date2`	No	YYYY-MM-DD end date (use with date1)
`dates`	No	Array of specific dates. Use either dates OR date1+date2
`competitor_id`	No
`type_range`	No	Date range type (default 2)
`only_exists_first_date`	No
`show_tops`	No
`show_avg`	No
`show_visibility`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 22, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the burden. It discloses return format ('dates array and seriesByProjectsId'), but does not explicitly state read-only behavior, side effects, authentication needs, or rate limits. It mentions 'single region' but omits the competitor_id parameter behavior.

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 sentences, front-loaded with the main action and resource, immediately followed by return value description. No unnecessary words, highly efficient.

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

Completeness4/5

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

Given the tool's complexity (11 parameters, no output schema), the description provides essential context: it returns chart data with dates and seriesByProjectsId. It does not detail nested structures or optional parameters, but it is sufficient for an agent to understand the tool's purpose and output. Slightly incomplete regarding competitor 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 45%, meaning some parameters are documented in the schema but many are not. The tool description adds general return context but no parameter-specific semantics beyond what the schema already provides. Baseline of 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 'Get chart data showing position distribution over time for a project and single region', using a specific verb and resource. It distinguishes from sibling tools like topvisor_get_summary (which provides summary data) by focusing on chart rendering with dates and seriesByProjectsId.

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 on when to use this tool vs alternatives. It does not mention prerequisites, exclusions, or scenarios where other tools would be preferred. The description only explains what it does, not 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