scraper_server_status
Check the status of all ScraperServer instances. Shows server health, circuit breaker state, failure counts, and last success/failure times.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
scrapi
TDQS
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Since no annotations are provided, the description carries the burden of behavioral disclosure. It indicates this is a status check (likely read-only) and lists the data shown, which gives some behavioral insight. However, it does not mention any side effects, permissions, or output format details.
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?
The description is two concise sentences, front-loaded with the main purpose, and every word adds value. There is no redundancy or fluff.
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?
Given the tool's simplicity (zero parameters, no output schema), the description adequately conveys what it does and what information it exposes. It lists the key data points (health, circuit breaker, failure counts, times) but could be slightly more explicit about the exact response structure. Still, it is largely complete for this simple tool.
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?
The tool has zero parameters, so the schema covers all parameter semantics (vacuously). The description adds no parameter details, but none are needed. Baseline 4 is appropriate for a zero-parameter tool.
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 clearly states a specific verb ('check') and resource ('status of all ScraperServer instances'), and the details (health, circuit breaker, failure counts) distinguish it from sibling tools like get_billing and scrape_url. It fully identifies the tool's purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives. It does not mention use cases, prerequisites, or when other tools might be more appropriate. This is a clear gap.
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.
TDQS
A3.8/5.0
Disambiguation4/5
get_billing and get_usage overlap somewhat in describing plan/credit information, but their distinct focus on billing details vs. usage/credits keeps them separable. scrape_url and scrape_urls are clearly differentiated by singular vs. plural operation. scraper_server_status is entirely distinct. Overall, the tools are mostly distinct with only mild ambiguity between billing and usage.
Naming Consistency3/5
Most tools follow a verb_noun pattern (get_billing, get_usage, scrape_url, scrape_urls), but scraper_server_status deviates as a noun phrase. This mixed convention is still readable and predictable, but not fully consistent.
Tool Count5/5
With 5 tools, the server is well-scoped for a scraping API. It covers single/batch scraping, server status, billing, and usage without unnecessary bloat, making the count appropriate for its purpose.
Completeness4/5
The tool surface covers the core lifecycle of a scraping service: scraping (single and multiple), health monitoring, and account management (billing/usage). Minor gaps exist, such as lack of detail on plan management or job cancellation, but these are not critical for the primary use case.