Skip to main content
Glama

AEORank — SEO, AEO & GEO Audit Engine

Lookup GEO-62 Rule & Pillar Weight

lookup_rule
Read-onlyIdempotent

Look up any of the 62 AEORank Technical SEO, AEO & GEO diagnostic rules (e.g. AEO-001..AEO-062, llms_txt, answer_first, entity_clarity) and 9-pillar weights.

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": {
      "query": "<query>"
    },
    "name": "lookup_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage for rule descriptions ('en' or 'vi').
queryYesRule code (e.g. AEO-001), rule ID (e.g. llms_txt_missing), or keyword.

Output Schema

NameRequiredDescriptionDefault
queryYes
matchesYes
matches_countNo
pillar_weightsNo
total_rules_in_standardYes
semantic_dimensions_countNo
agentic_readiness_signals_countNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so safety needs no restating. The description adds useful coverage facts (62 rules, 9 pillar weights) and example identifiers, but says nothing about miss/fallback behavior or how the 9 pillar weights relate to the rule results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence that states scope and immediately supplies concrete example tokens. Nothing is padded or redundant.

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 and annotations covering safety, the description needn't explain return values. For a simple two-parameter lookup it is nearly complete; only the pillar-weight lookup path and not-found behavior are left unstated.

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 coverage is 100% and the schema already spells out rule code, rule ID, and keyword with examples, so the description's example identifiers largely duplicate it. The only value added is the implication that pillar weights are also queryable, which the schema's 'keyword' wording doesn't make obvious.

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 gives a specific verb and resource ('Look up ... 62 AEORank Technical SEO, AEO & GEO diagnostic rules') and quantifies scope with the 9-pillar weights. It is clearly distinguishable from siblings like run_sandbox_audit or search_knowledge_playbooks, though it doesn't name an alternative 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?

Usage is only implied: the reader infers this is the tool for resolving a rule code or keyword, and the parenthetical examples hint at accepted query shapes. There is no statement of when to prefer this over search_knowledge_playbooks or what to do when a rule isn't found.

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.