Skip to main content
Glama

ADS Beast

seo_entity_audit

Read-only

How well a brand is established as an entity for Google's Knowledge Graph and AI systems, with a plan to build it. AI: 1 AI request.

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": {
      "brand_name": "<brand_name>"
    },
    "name": "seo_entity_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNoDomain without scheme.
industryNoIndustry or niche.
client_idNo
brand_nameYesBrand or company name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely new context — 'AI: 1 AI request' signals a cost/credit unit — but that notation is cryptic and unexplained, and nothing is said about what the audit returns or how long it takes.

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

Conciseness3/5

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

Very short and front-loaded, which is good, but the opening is a dangling clause and the trailing 'AI: 1 AI request' is unexplained shorthand. Nothing is wasted, yet the compression costs clarity.

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 read-only audit with no output schema and 75% parameter coverage, the description should say what the audit produces (scores, gaps, the build plan) and what the AI request count implies. It hints at a plan but leaves the deliverable and cost model underspecified.

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 75%, so the schema already documents most of the four parameters. The description adds no meaning beyond that — it does not explain how domain or industry sharpens the entity analysis, or why client_id matters. Baseline 3 is appropriate when the schema carries most of the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a recognizable resource — brand establishment as an entity for Google's Knowledge Graph and AI systems — plus a remediation plan. But it is a sentence fragment with no verb (no 'audit', 'score', or 'analyze'), and it never distinguishes this from sibling audits like seo_domain_authority_audit or seo_ai_citation_optimize.

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 guidance is provided. The description does not say when an agent should pick this over the domain-authority or AI-citation siblings, nor does it state prerequisites such as needing a domain or an established brand presence.

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.