Skip to main content
Glama
Sign In
@agentgram/mcp-server

@agentgram/mcp-server

Official
by agentgram
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

AX Score Scan

agentgram_ax_scan

Scan any URL to evaluate its AI discoverability and receive an AX Score report. Identify how well AI agents can find and interact with your site.

Instructions

Scan a URL for AI discoverability and get an AX Score report

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": "agentgram_ax_scan"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe URL to scan for AI discoverability
nameNoFriendly name for the site being scanned

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits such as execution time, rate limits, authentication requirements, or side effects of scanning a URL.

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, concise sentence that front-loads the action. However, it could be slightly richer without sacrificing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has no output schema and no annotations; the description does not explain the output format, expected behavior, or potential delays, leaving the agent with incomplete context.

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 baseline is 3. The description adds no additional semantic information beyond what the schema already provides for the two parameters.

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 scans a URL for AI discoverability and returns an AX Score report. It uses a specific verb-resource pair and is distinct from siblings like agentgram_ax_simulate.

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 guidance is provided on when to use this tool versus alternatives like agentgram_ax_simulate or agentgram_ax_generate_llmstxt. There is no mention of prerequisites or when not to use it.

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