Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

render-time-series-chart

Render an interactive line chart with hover tooltips, crosshair, toggleable legend, and automatic dual Y-axis for series with different units.

Instructions

Render an interactive line chart with hover tooltip and crosshair, a toggleable legend, and an automatic dual Y-axis when two series use different units. Fed by any history / daily-series tool (get_page_detail, get_keyword_detail, performance history…) that returns render_with: render-time-series-chart. Free.

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": "render-time-series-chart"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses rendering behavior (tooltip, crosshair, legend toggling, automatic dual Y-axis on mixed units) and the 'Free' cost trait, which are useful beyond a bare name. It does not say what input payload shape the chart expects, what happens on malformed or single-point data, or whether output is inline markup or a URL.

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?

Two sentences, front-loaded with the capability list before the data-source routing rule, with no filler. The trailing 'Free' is terse but genuinely informative about credit cost; a slightly clearer phrasing would be the only improvement.

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?

With no annotations, no output schema, and an empty open schema, the description has to establish purpose, data source, and rendering behavior, and it largely does. The remaining gap is how the caller must assemble the payload (presumably passed through from the upstream render_with hint), which is left implicit.

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

Parameters4/5

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

Parameter count is zero with an open additionalProperties schema, so the baseline is 4. The description does add meaning by explaining that inputs come from upstream tools that emit render_with: render-time-series-chart, which is the only hint an agent gets about what to pass into an otherwise untyped object.

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?

States a specific verb and resource ('Render an interactive line chart') and immediately enumerates the distinguishing features: hover tooltip, crosshair, toggleable legend, automatic dual Y-axis. An agent can tell this apart from render-data-table and render-scorecard from the description alone, without opening another schema.

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?

Gives a concrete trigger for use: any history or daily-series tool (get_page_detail, get_keyword_detail, performance history) that returns render_with: render-time-series-chart. That is an explicit routing rule to a real mechanism. It does not state when NOT to use it (e.g., categorical or multi-metric non-time data), which keeps it short of a 5.

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