Skip to main content
Glama
Sign In
dailyhot

dailyhot

by FrankXMX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

崩坏3

honkai

Retrieve current Honkai Impact 3rd updates. Accesses real-time game information from aggregated trending data across multiple platforms.

Instructions

获取崩坏3最新动态

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": "honkai"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
noCacheNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.13

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states 'get latest news', implying a read operation, but lacks details on caching, rate limits, data freshness, or potential side effects. This leaves significant gaps for the agent.

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

Conciseness3/5

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

The description is a single concise sentence, which is efficient for reading. However, it lacks substance and fails to earn its place due to missing critical information. It is under-specified rather than appropriately concise.

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

Completeness1/5

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

Given the absence of output schema, annotations, and parameter descriptions, the description is severely incomplete. The agent has no guidance on return format, parameter semantics, or expected behavior, making the tool difficult to use correctly.

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

Parameters1/5

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

Schema description coverage is 0%, yet the description does not explain the two optional parameters (limit, noCache). The agent cannot infer what 'limit' controls (e.g., number of results) or the effect of 'noCache'. This heavily burdens the agent to guess or rely on trial-and-error.

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?

Description clearly states the verb (获取=get) and resource (崩坏3最新动态=Honkai3 latest news). It distinguishes the tool from siblings that target other games or platforms, making purpose clear. However, it does not specify the content type or source.

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 is implied by the tool name and description: use when you need news about Honkai3. No explicit guidance on when not to use or alternatives among siblings, but the context of sibling tools (e.g., genshin, starrail) provides implicit differentiation.

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

Deploy Server

Other Tools