Skip to main content
Glama
Sign In
SEOctopus

SEOctopus

by itsjwill
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

performance_compare

Compare performance metrics of multiple web pages side-by-side to identify which pages load faster and need optimization. Supports desktop and mobile devices.

Instructions

Compare performance of multiple URLs side-by-side

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": {
      "urls": "<urls>"
    },
    "name": "performance_compare"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsYesURLs to compare (2-5)
deviceNoDevice typemobile

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so description must disclose behavioral traits. It only states 'compare performance' without specifying what metrics are compared, whether the operation is read-only, or what the response contains. Significant gaps for a comparison tool.

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?

Single sentence is concise and front-loaded, but could benefit from additional details without becoming verbose. No wasted words, but scope is limited.

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

Completeness2/5

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

Tool has 2 parameters, no output schema, and no annotations. The description is insufficient: no mention of return format, performance metrics, or read-only nature. For a comparison tool, more context is needed.

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?

Both parameters have schema descriptions (urls: 'URLs to compare (2-5)', device: 'Device type'), covering 100% of parameters. The tool description adds no additional meaning beyond what the schema already provides.

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 tool compares performance of multiple URLs side-by-side, which is a specific verb+resource combination that distinguishes it from sibling tools like performance_audit (single URL) and performance_cwv (focused on Web Vitals).

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 versus alternatives (e.g., performance_audit for single URL, competitive_analyze for broader comparison). Description lacks context about prerequisites or scenarios.

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