Skip to main content
Glama

BRAINIAC Technical SEO Audits

Analyse crawler hits in an access log

seo-technical_log-file-bot-analyze
Read-onlyIdempotent

Classify bot user-agents in Combined or W3C logs and verify Googlebot hits against vendored IP ranges. Price $0.04 USDC. POST /api/v1/seo-technical/log-file-bot-analyze. An unpaid call returns the x402 payment terms and does not run.

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": "<log>"
    },
    "name": "seo-technical_log-file-bot-analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
logYeslog, string, length 0 to 52428800. Required.
formatNoformat, string, one of combined, w3c. Required.combined
directoryDepthNodirectoryDepth, integer, from 0 to 20. Required.

Output Schema

NameRequiredDescriptionDefault
botsNobots. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.
parseErrorsNoparseErrors. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered; the description adds genuinely new behavioral facts: it costs $0.04 USDC via x402, and an unpaid call returns payment terms instead of executing. That failure mode is important and would otherwise surprise an agent. It stops short of noting the 50MB log cap or any processing limits, which the schema carries but the agent may not anticipate.

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?

Three short sentences, front-loaded with the capability before the commercial and transport details. The endpoint line ('POST /api/v1/...') is of marginal use to an agent and is the one element that doesn't clearly earn its place.

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?

With an output schema present, return values need not be described, and the payment/execution semantics are spelled out. The remaining gap is practical guidance on input size and the unexplained directoryDepth parameter for a read-only classification tool.

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%, so the parameters are already documented in structured data. The description only echoes the format values ('Combined or W3C logs') and says nothing about directoryDepth or how log size limits interact with the required log parameter, so it adds little beyond the schema.

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 names two specific operations on a specific resource: classify bot user-agents in access logs and verify Googlebot hits against vendored IP ranges. The mention of Combined/W3C input formats and Googlebot verification separates it from neighbors like crawl-depth-analyze or robots-txt-test, which operate on different artifacts.

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 context is implied by the input (an access log) and the purpose, but there is no explicit statement of when to choose this over sibling analyses such as crawl-depth-analyze, nor any prerequisites such as needing raw server logs. The only explicit conditional is about payment, not about task selection.

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