Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

render-scorecard

Render a KPI card grid from summary data, showing labels, raw values, optional units, period-over-period changes, and section grouping for clear performance snapshots.

Instructions

Render a KPI card grid from summary data — each card carries a label, a raw value, an optional unit ($ prefix, % suffix, or s for a duration), a period-over-period change with up/down direction, and optional grouping into sections when there are more than four cards. Auto-called when a summary tool (get_gsc_summary, get_ga4_summary…) returns render_with: render-scorecard. 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-scorecard"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it does disclose notable traits: unit rendering rules ($ prefix, % suffix, s for duration), the >4-card threshold that switches on section grouping, and that the call is 'Free' (no credit cost). It omits failure modes and what the tool hands back to the caller beyond a rendered grid.

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?

Front-loaded with the artifact, then the card contents, then the invocation trigger. Every clause contributes distinct information (units, direction, grouping threshold, auto-call, cost); nothing is restated from the name or repeated.

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?

For a parameterless, output-schema-less rendering tool with no annotations, the definition covers trigger, input shape, formatting, and grouping behavior, which is close to sufficient. The remaining gap is that the literal input contract is never pinned down because the schema accepts arbitrary properties.

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?

There are zero declared parameters (schema is a bare object with additionalProperties: true), which sets the baseline at 4. The description usefully characterizes the payload the card grid expects — per-card label, value, unit, change direction, grouping — which compensates for the empty schema without over-specifying.

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?

Names a specific verb and artifact: 'Render a KPI card grid from summary data', then enumerates the card anatomy (label, raw value, unit, period-over-period change, sectioning). That is enough to separate it from render-data-table and render-time-series-chart on artifact type. It stops short of an explicit contrast statement, so a 4 rather than a 5.

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 condition: 'Auto-called when a summary tool (get_gsc_summary, get_ga4_summary…) returns render_with: render-scorecard', naming the upstream producers explicitly. It does not state when an agent should prefer a different render tool or what to do if no render_with flag appears, but the primary invocation path is unambiguous.

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