Skip to main content
Glama

Index or remove a subdomain

index_subdomain

Add a subdomain of the agent's website to the index as a linked site (its pages join search and answers), or remove one with remove=true.

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": {
      "agent_id": "<agent_id>",
      "host": "<host>"
    },
    "name": "index_subdomain"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostYese.g. "shop.example.com"
removeNo
agent_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure, and it does explain the indexing effect ('its pages join search and answers'). It does not say whether removal deletes indexed content, whether the host must be verified/owned by the agent, whether the operation is idempotent, or what happens to already-indexed pages.

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 sentence with no wasted words: the primary action and its effect come first, and the alternate mode is appended with the exact flag that selects it. The parenthetical earns its place by explaining the consequence of indexing.

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 three-parameter mutation tool with no annotations and no output schema, the description covers the action and its effect but omits return behavior, error conditions, and whether removal is destructive to indexed pages. It is adequate to attempt a call but not complete enough to predict outcomes confidently.

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 only 33%, so the description should compensate more. It does add real meaning for the `remove` flag (remove=true triggers deletion rather than addition), but leaves `agent_id` and `host` undocumented beyond the schema's single example value, and does not state format constraints on host.

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 states a specific verb and resource ('Add a subdomain ... to the index as a linked site') and immediately explains the effect ('its pages join search and answers'), plus the inverse mode via remove=true. It does not name a sibling such as add_site_pages or get_site_index_status, so differentiation is left implicit.

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 description clarifies the two operating modes (default add vs. remove=true), which is genuine usage guidance for the parameter. However, it offers no guidance on when to prefer this tool over related siblings like add_site_pages or when to check status first, and no prerequisites are stated.

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