Skip to main content
Glama

netcafe-china

by com.ainetcafe

Find the right tool for a task

what_can_you_do
Read-onlyIdempotent

Describe a task in plain language (any language) and get back exactly which tools on this server do it, with ready-to-run example calls — instead of reading the whole catalogue and guessing. Also returns multi-step recipes when a task needs several tools chained (invoices to a ledger, a bank statement reconciled, a messy CSV turned into a deliverable). Deterministic and free: it calls no model, costs nothing, and never runs out of quota. Call this FIRST when you are not sure what this server offers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesWhat you are trying to do, e.g. "reconcile a bank statement against my books" or "把一堆发票整理成能入账的表格"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover non-destructive, read-only, idempotent behavior. Description adds valuable context: it is deterministic, calls no model, costs nothing, and never runs out of quota, plus clarifies it returns example calls and recipes. This exceeds the structured hints without contradicting them.

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?

Four sentences pack purpose, features, behavioral guarantees, and usage guidance with no redundancy. Front-loaded with main action, then supporting details.

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?

For a single-parameter meta-tool with output schema present, the description explains what it returns, when to use it, and behavioral guarantees. Nothing major is missing.

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 covers 100% of parameter info, with a clear description and examples for 'task'. Description adds no additional parameter semantics; baseline of 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 identifies the tool as a meta-tool that maps plain-language tasks to server tools, with ready-to-run examples and multi-step recipes. This sharply distinguishes it from sibling domain-specific tools like bazi_chart or phone_info.

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

Usage Guidelines5/5

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

Explicitly instructs to call this FIRST when unsure of server offerings, and frames itself as an alternative to reading the whole catalogue and guessing. Provides clear context for when this tool is appropriate.

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

All netcafe-china 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

A3.7/5.0
Disambiguation4/5

Most tools are clearly distinct: bazi_chart, lunar_calendar, huangli, pick_lucky_days all relate to Chinese calendrical/astrological concepts but have different purposes (birth chart, lunar info, almanac, lucky day selection). However, bazi_chart and lunar_calendar both touch on 干支/zodiac; pick_lucky_days could overlap with huangli. Minor ambiguity, but descriptions clarify.

Naming Consistency4/5

Tool names are all snake_case and mostly descriptive, but they don't follow a strong verb_noun pattern (e.g., pick_lucky_days is verb+noun, but bazi_chart and phone_info are noun-like). Slight inconsistency in style, but the pattern is predictable enough.

Tool Count5/5

10 tools is well-scoped for a China-focused utility server. Each tool serves a distinct purpose (ID validation, phone info, holidays, calendar, pinyin, network reachability), and the count feels reasonable without being bloated or thin.

Completeness3/5

The server covers a broad range of China-specific utilities, but there are gaps: no tool for Chinese address parsing, no tool for bank card validation, no tool for translation. While the existing set covers common needs, the 'china' theme could benefit from more coverage. Also, what_can_you_do suggests recipes but the actual tool set lacks some common use cases.

Resources