Skip to main content
Glama
Sign In
dailyhot

dailyhot

by FrankXMX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

崩坏星穹铁道

starrail

Retrieves current trending posts and updates from Honkai: Star Rail communities by aggregating data across platforms. Provides real-time content for game updates and discussions.

Instructions

获取星穹铁道最新动态

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

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?

With no annotations, the description carries full burden but only states 'get latest updates'. It does not disclose caching, rate limits, or potential side effects. The parameter 'noCache' hints at caching behavior but is not mentioned.

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?

The description is a single, concise sentence that immediately conveys the tool's purpose. It is front-loaded but could benefit from more structure.

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

Completeness2/5

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

Given no output schema and 0% parameter coverage, the description is incomplete. It fails to specify the nature of the updates or how parameters affect results, leaving an agent underinformed.

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% and the description adds no meaning to the parameters. It does not explain what 'limit' controls or the role of 'noCache'.

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?

The description clearly states the tool retrieves latest updates for Star Rail. However, it does not differentiate from sibling tools like 'genshin' or 'honkai' for other games.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions.

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