Skip to main content
Glama

netcafe-almanac

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.9/5.0
Behavior5/5

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

Annotations already declare read-only and non-destructive. The description adds that it is deterministic, calls no model, costs nothing, never runs out of quota, and can return multi-step recipes, which goes beyond the annotation basics.

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, each earning its place: purpose, recipe behavior, cost/performance, and usage instruction. Front-loaded with the main purpose, no redundancy.

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 one-parameter discovery tool with an output schema and robust annotations, the description covers purpose, usage, behavior, and edge cases. Nothing important is missing.

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 schema already covers the single 'task' parameter with examples. The description adds that it accepts any language and emphasizes plain-language input, providing modest extra context beyond the schema.

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 it maps plain-language tasks to the exact tools on this server, with example calls. This is a specific verb+resource and is easily distinguished from sibling domain tools like bazi_chart or cn_holiday.

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 'Call this FIRST when you are not sure what this server offers' and contrasts with 'reading the whole catalogue and guessing'. This gives unambiguous when-to-use and alternative scenarios.

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

All netcafe-almanac 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.1/5.0
Disambiguation5/5

Each tool targets a narrow, distinct concern: bazi_chart for birth charts, cn_holiday for public holidays, huangli for daily auspicious items, lunar_calendar for lunar dates, and pick_lucky_days for selecting dates. There is no meaningful overlap; even the related huangli and pick_lucky_days are clearly separated by direction (given date vs. searching dates).

Naming Consistency3/5

All names are lowercase snake_case, so style is consistent, but the grammatical pattern is mixed: bazi_chart and huangli are nouns, lunar_calendar is an adjective-noun, pick_lucky_days is verb-object, and what_can_you_do is a sentence. This is readable but lacks a uniform verb_noun convention.

Tool Count5/5

Six tools is a well-scoped set for a Chinese almanac/calendar server. Each tool covers a distinct major feature (charts, holidays, almanac, lunar info, date selection) with no redundancy, and the count is comfortably within the ideal 3-15 range.

Completeness5/5

The server covers the core needs of its domain: lunar conversion, public holidays, daily almanac rulings, lucky date selection, and bazi charts. There are no obvious dead ends; the addition of what_can_you_do also helps agents navigate the remaining surface, making the set feel comprehensive for its intended purpose.

Resources