Skip to main content
Glama
Sign In

Teddit

by io.teddit
OverviewDiscussionsAdmin

AI crawler access

get_crawler_access
Read-onlyIdempotent

Check what the site’s robots.txt lets each AI crawler (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Googlebot, Google-Extended, …) read: allowed, blocked or some paths closed, with the deciding robots.txt line, whether llms.txt exists, and what changed since the check before. Use it when a site is rarely linked, to rule out blocked crawlers. check=true re-reads robots.txt now (needs a member token or above); otherwise the last check is returned.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_crawler_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkNotrue re-reads robots.txt now; leave out for the last check.
projectIdYesThe project id, from list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that check=true re-reads robots.txt immediately and requires a member token or above, while omitting it returns the last check. It also describes the returned content in useful detail, including deciding robots.txt lines and changes since the prior check.

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 front-loaded with the primary check and then provides usage and parameter behavior. It is dense but each sentence adds purpose, usage, or behavioral context; minor trimming could improve scannability, but nothing is wasted.

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

Completeness5/5

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

With no output schema, the description still explains the relevant return values (allowed/blocked status, deciding line, llms.txt, and changes). It also covers the important behavioral distinction between fresh and cached checks and the token requirement, leaving no significant gap for an agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents both parameters. The description adds meaningful context by stating that check=true requires a member token or above and that omitting it returns a cached result, though projectId is left to the schema's reference to list_projects.

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 specifies the exact verb and resource: checking what a site's robots.txt permits for named AI crawlers. It also enumerates the returned details (allowed/blocked status, deciding line, llms.txt existence, changes since last check), making the tool's scope unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear usage scenario: use when a site is rarely linked, to rule out blocked crawlers. It also explains the fresh-check versus cached-result behavior. No explicit alternatives or when-not-to-use guidance are provided, but the context is sufficiently clear.

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

All Teddit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources