Skip to main content
Glama

Caelara Labs SEO & GEO Readiness

technical_seo_composite

Technical SEO audit: redirects, meta, canonical, headings, hreflang, schema, robots.txt with scored issues

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": "technical_seo_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL to audit

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the burden, and it does disclose one real behavioral fact: results come back as 'scored issues'. It leaves open whether the tool fetches live content, whether scope is a single page or a whole site (relevant given the robots.txt check), and whether it is strictly read-only.

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?

A single front-loaded sentence naming the operation first, then the check inventory. Dense but every token carries information; slightly clipped for the amount of behavior it must convey.

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?

For a one-parameter composite audit with no output schema, the description covers what is checked and that results are scored, but omits return structure detail and crawl/scope behavior that materially affect correct invocation.

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?

One parameter at 100% schema coverage, so the schema already defines 'url'. The description's 'Page URL' phrasing adds a useful scope signal (single page, not domain), but nothing about accepted formats or redirect handling.

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 operation on a specific resource (technical SEO audit) and enumerates the exact check categories: redirects, meta, canonical, headings, hreflang, schema, robots.txt. The breadth of that list implicitly separates it from the single-purpose siblings (hreflang_validator, schema_org_validator), though it never says so outright.

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 when-to-use, when-not, or alternative is stated. An agent has to infer from the enumerated checks that this is the broad-sweep option versus the focused validators, rather than being told so.

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