Skip to main content
Glama
Sign In

fetchgate

by dev.fetchgate
OverviewDiscussionsAdmin

Get Agent Web Crawler Census

get_agent_census

Return the Agent Web Crawler Census: every named bot observed crawling a live, publicly-listed x402 + MCP endpoint over a 24-hour window, each with a case-insensitive regex matcher and a behavioural category (liveness-monitor, directory-crawler, price-scraper, security-research, ai-training, ...) so you can classify your own access log. Observed first-hand, not aggregated from third-party bot lists. Notable finding: of the named agent-web crawlers in the census, zero have ever presented a payment, and several declare that in their own User-Agent string. Wraps GET /v1/agent-census.json. Free, unmetered, no payment required. CC BY 4.0.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_agent_census"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryNoOptional. Return only agents in this behavioural category, e.g. "price-scraper" or "liveness-monitor". Omit for the full census.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It adds substantial context beyond the action: data is 'observed first-hand, not aggregated from third-party bot lists', it wraps GET /v1/agent-census.json, and it is 'free, unmetered, no payment required' with 'CC BY 4.0'. It also reveals a notable behavioral finding (zero crawlers presented payment). It does not explicitly discuss side effects, but the GET/read nature is clear.

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 longer than a two-sentence definition, but each sentence earns its place: content, provenance, notable finding, endpoint, cost, and license. The core purpose is front-loaded, though the 'Notable finding' sentence is slightly discursive for tool invocation purposes.

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?

The tool is simple: one optional parameter, no required parameters, no output schema. The description explains what will be returned (bots with matcher and category), the filtering dimension, the 24-hour window, the wrapped endpoint, and the absence of cost/authentication requirements. This is sufficient for an agent to invoke it correctly.

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% and the single optional 'category' parameter is already well documented in the schema with examples. The description adds a few extra category examples (directory-crawler, security-research), but this is marginal and does not materially change parameter understanding. Baseline 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 opens with a specific verb and resource: 'Return the Agent Web Crawler Census'. It then explains precisely what the census contains (named bots, case-insensitive regex matcher, behavioural category) and the use case (classifying access logs). It is clearly differentiated from sibling tools like get_metadata or list_products.

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 a usage context ('so you can classify your own access log') and notes it is free/unmetered, but it does not explicitly state when to choose this tool over siblings or provide exclusions. No alternative tools are named or contrasted.

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

All fetchgate 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