Skip to main content
Glama
Sign In
geo-inspector-mcp

geo-inspector-mcp

by Bigsupe55
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Check indexing and AI meta directives

check_meta_directives

Inspects a webpage's meta robots tags and X-Robots-Tag headers to report indexing directives.

Instructions

Report indexing directives from meta robots tags (including bot-specific and noai/noimageai tags) and X-Robots-Tag response headers for a page.

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": {
      "url": "<url>"
    },
    "name": "check_meta_directives"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesWebsite URL. Scheme is optional, example.com works.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries full burden. It describes what the tool reports but does not disclose behavioral traits like read-only nature, error handling, or authentication requirements. It is adequate but lacks depth for a standalone description.

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?

The description is a single, well-structured sentence that is front-loaded with the core action ('report indexing directives') and includes specific details. Every word earns its place, with no redundancy.

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?

For a simple one-parameter tool with no output schema, the description covers the main functionality. It could mention what happens on error or hint at output format, but overall it is reasonably complete for the tool's complexity.

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% for the single 'url' parameter, which already documents its type and format. The tool description adds no additional meaning beyond the schema, so the baseline score of 3 applies.

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 clearly states the tool's purpose: reporting indexing directives from meta robots tags and X-Robots-Tag headers. It specifically mentions bot-specific and noai/noimageai tags, distinguishing it from siblings like check_robots_txt (site-level), fetch_llms_txt, and detect_schema_markup.

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 implies usage for checking page-level meta directives but provides no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives or exclude scenarios, leaving the agent to infer from siblings.

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

Deploy Server

Other Tools