Wenbu · 问卜

get daily card

get_daily_card

Read-onlyIdempotent

Get a public daily reflection card and practice using the server calendar in an IANA timezone. No model, account, personal history or quota turn. Can differ from a personal browser/account card. Keep the returned result for follow-up.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_daily_card"
  }
}

Input Schema

Name	Required	Description	Default
`locale`	No		en
`timezone`	No		UTC

Output Schema

Name	Required	Description	Default
`note`	Yes
`clock`	Yes
`scope`	Yes
`result`	Yes
`practice`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely non-obvious context: no quota turn is consumed, no account/personal history is involved, and the card may differ from an account-based card. The instruction to 'keep the returned result for follow-up' hints that no server-side session persists, which is useful behavioral signal beyond the annotations.

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

Conciseness4/5

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

Four short sentences, front-loaded with the core action and scoping caveats, with no filler. The phrase 'and practice using the server calendar' is awkward and slightly muddies the opening sentence, but overall it is tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be explained, and the no-quota/no-account behavior is covered. The gaps are the undocumented locale parameter, ambiguity around what 'the server calendar' means versus the timezone parameter, and no indication of what 'follow-up' entails beyond keeping the result.

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 description coverage is 0%, so the description carries the burden. It clarifies the timezone parameter as an IANA timezone, but the locale parameter and its zh/en enum are never mentioned, and the description's phrasing about 'the server calendar' is ambiguous about whether timezone governs the card's date or only timestamp handling.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get a public daily reflection card') and marks it as public, which separates it from anything account- or model-based. However, it never names a sibling tool or explains how it differs from calculate_bazi/draw_tarot-style tools, so differentiation is inferred rather than explicitly stated.

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

Usage Guidelines3/5

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

Usage context is implied ('No model, account, personal history or quota turn', 'Can differ from a personal browser/account card'), which tells an agent this is a stateless public lookup rather than a personalized one. There is no explicit when-to-use/when-not or named alternative among the sibling tools, so the agent must infer the routing itself.

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

All Wenbu · 问卜 tools Inspect

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.