@lodd/mcp-server

get_performance

Retrieve page load time metrics grouped by URL, device, country, or browser to identify slow pages and analyze performance impact on engagement.

Instructions

Get page load time metrics (average, median, p95) grouped by page URL, device type, country, or browser. Only includes data from pages with load time measurements. Useful for identifying slow pages and correlating performance with engagement.

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": {
      "site": "<site>"
    },
    "name": "get_performance"
  }
}

Input Schema

Name	Required	Description	Default
`site`	Yes	Site domain or UUID
`limit`	No	Max results (1-1000)
`period`	No	Time period	30d
`group_by`	No	Dimension to group by	page

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.15Jul 28, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations provided, so description carries burden. It describes what is returned and that it includes filtered data, but does not explicitly state read-only nature or disclose authentication/rate limit requirements.

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, no redundancy, front-loaded with main action and then context.

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?

Adequate for a performance metrics tool with 4 parameters, though missing details like how period affects data and no output schema. Still sufficiently complete for agent to understand functionality.

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?

Schema covers all 4 parameters with descriptions, but description adds value by explaining grouped dimensions and output metrics (average, median, p95), which are not in schema.

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?

Description clearly states the verb 'Get' and resource 'page load time metrics' with specific metrics (average, median, p95) and grouping dimensions. Distinct from sibling tools focusing on other analytics.

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?

Describes condition 'Only includes data from pages with load time measurements' and suggests use case 'identifying slow pages', but does not provide explicit when-to-use vs alternatives or when-not-to-use.

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