Skip to main content
Glama

netcafe-tasks

by com.ainetcafe

Test if a URL is reachable from mainland China

china_reachability
Read-onlyIdempotent

Fetch a URL from a real mainland-China network egress and report HTTP status, latency and China DNS resolution. Answers "is my site/API usable from China?" with a measurement instead of a guess — you cannot get this from a VPS abroad.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesFull URL to test, e.g. https://example.com

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only/idempotent annotations, the description discloses that it fetches from a real mainland-China egress and reports three metrics (HTTP status, latency, China DNS resolution). This gives the agent a concrete model of the operation without needing to infer.

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 well-structured sentences, front-loaded with the action and output, and the explanatory value proposition is concise. No wasted words.

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 only one parameter and an output schema present, the description covers the tool's purpose, method, and key return data. Siblings are unrelated, and no additional context is needed for tool selection.

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 schema covers 100% of the single parameter with a clear description ('Full URL to test'), so the description adds no additional parameter semantics. Baseline 3 is appropriate.

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?

Description clearly states it fetches a URL from a real mainland-China network egress and reports HTTP status, latency, and DNS resolution. The purpose—testing China reachability—is specific and distinct from the unrelated sibling task-management tools.

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?

The description frames when to use: to get a measurement-based answer to 'is my site/API usable from China?' and notes why a VPS abroad cannot provide this. It doesn't enumerate explicit 'when not to use' cases, but the context is clear and sufficient for this tool.

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

All netcafe-tasks toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

The task lifecycle tools (create_task, delete_task, get_task_runs, list_tasks) are clearly distinct, and china_reachability is a direct one-off measurement while what_can_you_do is a meta helper. The only mild ambiguity is that create_task can create a watch_reachability schedule, which overlaps conceptually with china_reachability, but the descriptions clarify one-off versus scheduled.

Naming Consistency3/5

create_task, delete_task, get_task_runs, and list_tasks follow a clear verb_noun pattern, but china_reachability is a noun-phrase measurement tool and what_can_you_do is an idiomatic helper phrase. The set is readable but mixes naming conventions.

Tool Count5/5

Six tools is well-scoped for a scheduled-task server covering creation, deletion, listing, run inspection, a direct reachability check, and self-help. Each tool earns its place and there is no obvious bloat or thinness.

Completeness3/5

The core scheduled-task lifecycle is covered: create, list, inspect runs, and delete. However, there is no update_task or pause/resume capability, so changing a task's schedule or configuration requires deleting and recreating it, which also loses run history. That is a notable operational gap.

Resources