Skip to main content
Glama
Sign In

Xcatcher — Recent X Posts

by io.github.lvpiggyqq
OverviewDiscussionsAdmin

Preflight an Xcatcher crawl for free

preflight_crawl
Read-onlyIdempotent

Normalize and deduplicate X handles, validate the mode, and preview the current modeled points/USDC cost. This free read-only check requires no account, creates no quote or task, and moves no funds. Use it before requesting a live x402 payment challenge.

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": {
      "users": "<users>"
    },
    "name": "preflight_crawl"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoAPI-key accounts use 1 point per normal handle and 10 per deep handle; direct x402 normal requests receive progressive batch pricing shown by preflight.normal
usersYesX handles, @handles, or x.com/twitter.com profile URLs.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / mode / description
      Previous value: -"normal costs 1 point-equivalent per handle; deep costs 10."New value: +"API-key accounts use 1 point per normal handle and 10 per deep handle; direct x402 normal requests receive progressive batch pricing shown by preflight."
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false), the description adds concrete side-effect guarantees: 'requires no account', 'creates no quote or task', and 'moves no funds'. It also describes the normalization/deduplication behavior, which is not present in annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, each dense with information. The first lists core actions, the second clarifies safety and usage. No redundant or filler content.

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?

Given an output schema exists, return values are already specified. The description covers the tool's purpose, when to use it, and its side-effect profile. For a 2-parameter tool with fully described schemas, this is complete.

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?

The input schema already covers both parameters with detailed descriptions (mode pricing, users formats), and schema coverage is 100%. The description's mention of 'validate the mode' and 'preview cost' aligns with the schema but adds no new semantic detail beyond the parameter descriptions.

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 uses specific verbs ('Normalize and deduplicate', 'validate', 'preview') and names the resource ('X handles' and 'modeled points/USDC cost'). It clearly distinguishes this tool from siblings like get_x402_quote or create_crawl_task by framing it as a preflight check that creates no quote or task.

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?

Explicitly states 'Use it before requesting a live x402 payment challenge', giving clear temporal guidance. Also notes 'requires no account' and 'creates no quote or task', implying when to use this instead of tools that require accounts or create tasks. However, it does not explicitly name alternative tools or state 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.

All Xcatcher — Recent X Posts 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