AEO Copilot MCP Server

create_index

Create a brand-agnostic industry index to track every entity cited across AI prompts, giving a clear view of an industry without focusing on any single brand.

Instructions

Create an industry index — a brand-agnostic view of an industry that tracks every entity cited across prompts (no single brand is the focus).

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": {
      "name": "<name>",
      "industry": "<industry>"
    },
    "name": "create_index"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Index name
`industry`	Yes	Industry or vertical the index covers
`description`	No	What this index is tracking

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.2.0Aug 30, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the behavioral transparency burden. It describes the conceptual purpose but does not disclose side effects, such as whether creating the index triggers prompt scanning, whether it is idempotent, what permissions are required, or what the response looks like.

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 description is a single sentence with the key verb and resource front-loaded. The parenthetical 'no single brand is the focus' is slightly redundant with 'brand-agnostic' but reinforces the distinction without adding much length.

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 simple creation tool with fully documented parameters, the description is mostly adequate: an agent knows what to create and what the index represents. However, with no output schema and no annotations, the expected response, error conditions, and follow-up steps such as adding topics or prompts are left unspecified.

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%, so the baseline is 3. The description adds context about what an industry index is, but it does not extend the meaning of the individual parameters beyond their schema descriptions.

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

Purpose5/5

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

The description states a specific verb and resource ('Create an industry index') and clearly defines its unique role as a 'brand-agnostic view of an industry that tracks every entity cited across prompts.' This distinguishes it from brand-focused siblings like create_brand and from topic-related tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description conveys when to use this tool: when the goal is an industry-wide, brand-agnostic tracking view rather than a single-brand focus. It does not explicitly name alternatives or state hard when-not-to-use conditions, so it falls just short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.