Skip to main content
Glama

Honest seo audit intent map — Atom

Honest SEO audit intent map

honest_seo_audit_intent_map
Read-onlyIdempotent

Submits an SEO audit and search-intent map record (technical foundation, intent map and on-page craft, structured data and entity clarity, earned authority and measurement, white-hat red lines) and returns a deterministic HONEST_SEO_MAP_SOUND / HONEST_SEO_MAP_NOT_SOUND / INSUFFICIENT_EVIDENCE verdict across five sections, including computed per-page intent-ownership and coverage checks, with per-check evidence. Audits the declared record; it crawls nothing and reads no live data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "honest_seo_audit_intent_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteNoSite or property the audit covers.
pagesNoDeclared pages: {name, intent, intent_type, has_single_intent, fully_answers_question}.
ai_eraNoAI-era extraction evidence.
entityNoEntity clarity evidence.
intentNoIntent map evidence.
on_pageNoOn-page craft evidence.
authorityNoEarned authority evidence.
red_linesNoWhite-hat red-line evidence.
technicalNoTechnical foundation evidence.
measurementNoMeasurement evidence.
structured_dataNoStructured data evidence.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds genuinely non-redundant context: the verdict is deterministic, it resolves to one of three named outcomes across five sections, and it includes computed per-page intent-ownership and coverage checks with per-check evidence. Most useful is the explicit clarification that no crawling or live reads occur, which prevents the agent from misreading 'audit' as an active scan.

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?

Three sentences, front-loaded with the action and its return contract, followed by the scope caveat. It is dense but every clause carries information, and the final sentence is well placed as a guard against misreading the tool as a crawler.

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 11 parameters, nested objects, and no required fields, this could easily under-specify, but the description compensates by explaining the return contract (three verdict values, five sections, per-check evidence) despite there being no output schema. It stops short of explaining what constitutes sufficient evidence or how a verdict is derived, which would matter for a zero-required-field validation tool.

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% across 11 parameters, so the baseline is 3. The description enumerates the five audit areas that map loosely onto the section parameters (technical, intent, on-page, structured_data, authority, measurement, red_lines) and references per-page computation for 'pages', but it adds no format, unit, or required-evidence guidance beyond the schema.

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?

Specific verb and resource: it submits an SEO audit / search-intent-map record across five named sections and returns a deterministic verdict. The verdict token names (HONEST_SEO_MAP_SOUND / NOT_SOUND / INSUFFICIENT_EVIDENCE) make the outcome concrete. It loses a point only for density of jargon that slows first-read comprehension, though the purpose is still unambiguous.

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 closing sentence establishes a key usage constraint: the tool audits a declared record and 'crawls nothing and reads no live data', telling the agent it must supply evidence rather than expect fetching. However, there is no explicit when-to-use framing, no prerequisites, and no statement about when the INSUFFICIENT_EVIDENCE path is the expected outcome versus a failure.

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.