Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_seo_geo_readiness_composite

Assess a page's generative-engine readiness: score llms.txt, AI crawler access, structured data, and content clarity to find SEO/GEO gaps.

Instructions

[SEO & GEO Readiness] Generative-engine readiness score: llms.txt + AI crawler access + structured data + content clarity Measured p50 13 ms, p95 15 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://seo.caelaralabs.com.

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": {
      "url": "<url>"
    },
    "name": "caelara_seo_geo_readiness_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL to assess

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It does disclose useful context beyond the schema — the external host it calls (https://seo.caelaralabs.com) and measured latency (p50 13 ms, p95 15 ms with a benchmark date), which helps with timeout/ordering decisions. It says nothing about auth requirements, rate limits, whether the call is a safe read, or what happens on unreachable pages.

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?

The score definition is front-loaded in the first clause and the operational metadata (latency, endpoint) follows, so an agent gets the essentials immediately. The unpunctuated signal list reads slightly run-on and costs a moment of parsing, but nothing is padding.

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

Completeness3/5

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

There is no output schema, so the description is the only place an agent could learn what the score actually returns — scale, per-signal breakdown, or verdict fields — and it does not say. For a composite that aggregates four checks into a score, that missing return-shape information is the main gap; the endpoint and latency notes partially offset it.

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% — the single `url` parameter is already documented as 'Page URL to assess'. The description adds no meaning beyond that: no guidance on whether the URL must be absolute, whether redirects are followed, or whether a homepage vs. deep page matters. Baseline 3 applies when the schema does the work.

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?

The description names a specific deliverable — a 'Generative-engine readiness score' — and enumerates the four signals it aggregates (llms.txt, AI crawler access, structured data, content clarity). That is enough for an agent to tell it is the aggregate check rather than a single-signal sibling like caelara_seo_llms_txt_auditor, though no sibling is named explicitly.

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?

The 'composite' framing and the bracketed [SEO & GEO Readiness] category imply this is the overall assessment to use instead of running individual checks, but the description never states when to prefer it over the single-signal tools or what prerequisites exist. Usage is left to inference.

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