Skip to main content
Glama
AI1379
by AI1379

genshin_daily_note

Retrieve Genshin Impact daily note data for resin, realm currency, commissions, and expeditions. Provide account_id when multiple accounts are active; otherwise omit it.

Instructions

Genshin Impact real-time note: resin, realm currency, commissions and expeditions. account_id from accounts_list; omit when only one account is logged in.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNo
Behavior3/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It does state the data returned and the real-time nature of the note, which is useful, but it does not mention authentication requirements, side effects, failure behavior, or refresh/rate implications.

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 short, information-dense sentences. The primary output information comes first, followed by the parameter guidance. Every phrase earns its place with no redundant wording.

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?

For a single optional-parameter read-style tool, this is nearly complete: it lists the returned data categories and explains how to handle account selection. Some additional context about requiring an authenticated Genshin account could strengthen it, but the mention of accounts state and acounts_list makes the expectation reasonably clear.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema only provides the parameter name, an optional string/null type, and a default of null. The description adds meaningful semantics by explaining where account_id comes from and exactly when it should be omitted, fully compensating for the schema's 0% description coverage.

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 identifies the tool as a Genshin Impact real-time note and lists the specific data it covers: resin, realm currency, commissions, and expeditions. This is precise enough to distinguish it from sibling tools like starrail_daily_note and zzz_daily_note.

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 provides practical usage guidance for the account_id parameter: source it from accounts_list and omit it when only one account is logged in. It does not explicitly name sibling alternatives or give when-not-to-use guidance, but the intended context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AI1379/mihoyo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server