Skip to main content
Glama
CiteContext MCP Server

CiteContext MCP Server

analyze_agent_logs

Parse raw web server or edge access logs to identify AI crawler traffic, status codes, and blocked paths, so you can audit crawler access and diagnose blocked AI bots.

Instructions

Parse raw web server or edge access logs to identify incoming AI crawler traffic (GPTBot, ClaudeBot, PerplexityBot, Google-Extended), status codes, and blocked paths.

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": {
      "log_data": "<log_data>"
    },
    "name": "analyze_agent_logs"
  }
}

Input Schema

NameRequiredDescriptionDefault
log_dataYesRaw web server access log lines (CLF, Combined, or JSON lines)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full disclosure burden. It does add valuable behavioral context by naming the exact bots detected and the derived outputs (status codes, blocked paths), but it says nothing about input size limits, whether the log data is stored or transient, error handling on malformed lines, or whether the analysis touches server configuration.

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?

A single front-loaded sentence with the action first and the detected entities after. Every clause carries information; the only mild weakness is that the bot list and output list are packed into one long clause rather than separated for scannability.

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 one-parameter read-only analysis tool with no output schema, the description covers what goes in (raw access logs), what is detected, and what categories of result come back. Remaining gaps, chiefly input size and output shape, are minor for a tool of this 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?

There is one parameter at 100% schema coverage: the schema already documents that log_data takes raw lines in CLF, Combined, or JSON lines format. The description adds no format syntax, escaping rules, or size expectations beyond that, so the schema does the work and the baseline of 3 applies.

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 gives a specific verb ('Parse') tied to a specific resource ('raw web server or edge access logs') and enumerates the extracted entities: named AI crawlers, status codes, and blocked paths. It is clearly distinguishable from siblings like check_ai_bot_access or analyze_gsc_ai_overviews, though it never explicitly names them, so it stops short of a 5.

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?

Usage is only implied by the input type: the agent must infer that this tool applies when it already holds raw log lines rather than a config or domain. There is no explicit when-to-use/when-not statement and no routing away from the similarly themed check_ai_bot_access, so an agent could plausibly pick the wrong one.

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