Skip to main content
Glama

BRAINIAC Technical SEO Audits

Rate p75 Core Web Vitals

seo-technical_core-web-vitals-assess
Read-onlyIdempotent

Rate caller-supplied p75 LCP/INP/CLS/FCP/TTFB against web.dev thresholds and rank URL groups by failing CWV. Price $0.02 USDC. POST /api/v1/seo-technical/core-web-vitals-assess. An unpaid call returns the x402 payment terms and does not run.

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": {
      "groups": "<groups>"
    },
    "name": "seo-technical_core-web-vitals-assess"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupsYesgroups, array. Required.

Output Schema

NameRequiredDescriptionDefault
groupsNogroups. Array.
rankingNoranking. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description goes further by disclosing cost ($0.02 USDC), the x402 payment gating, the HTTP method/path, and crucially that an unpaid call returns payment terms without running. That last point is real behavioral context an agent cannot get from the annotations.

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?

Four short sentences, front-loaded with the capability before the pricing and endpoint metadata. The literal 'POST /api/v1/...' path is marginally useful filler for an agent but is compact and does not obscure the core statement.

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 an output schema present, return shapes need no explanation, and the payment/auth preconditions are explicitly covered. The one gap is that group-level device handling and the presence of fidMs in the payload are left entirely to the schema, but nothing required to call it correctly is missing.

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 100%, so the baseline is 3. The description adds only the threshold source (web.dev) that gives meaning to the supplied numbers; it omits the schema's fidMs field and the device parameter entirely, leaving the schema to carry parameter detail.

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 ('Rate'), a specific resource ('caller-supplied p75 LCP/INP/CLS/FCP/TTFB'), the benchmark used (web.dev thresholds), and a second output behavior ('rank URL groups by failing CWV'). The phrase 'caller-supplied' implicitly distinguishes it from the crawl/link/robots siblings that gather their own data.

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?

Usage is implied rather than stated: an agent can infer you call it when you already hold p75 metric data, and that it will not fetch data itself. There is no explicit when-not guidance or named alternative among the technical-audit siblings, so the guidance remains implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources