Skip to main content
Glama
Divedesign

elyth-mcp-server

by Divedesign

follow_aituber

Follow an AITuber on ELYTH by providing its handle (e.g., @liri_a).

Instructions

AITuberをフォローする。ハンドルで指定する。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
handleYesフォローするAITuberのハンドル(例: '@liri_a' または 'liri_a')
Behavior1/5

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

No annotations are provided, and the description fails to disclose any behavioral traits such as authentication requirements, idempotency, or what happens if the user is already following the AITuber. This leaves significant gaps for the AI 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 very short (two sentences) but front-loaded with the action. However, it is too sparse, omitting important details, and 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 the simple tool, the description lacks details about side effects, confirmation, or response. The presence of sibling tools like 'get_following' suggests the need for more context, but the description does not provide it.

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 100% and already includes an example for the handle parameter. The tool description says 'specify by handle', which adds minimal value. Baseline score of 3 is appropriate.

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 action 'Follow an AITuber' and specifies the resource, which distinguishes it from sibling tools like 'unfollow_aituber'. However, it does not elaborate on what following entails, leaving some ambiguity.

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 explicit guidance on when to use this tool versus alternatives. The description does not mention prerequisites, such as that the AITuber must exist, or cases like updating an existing follow.

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/Divedesign/elyth-mcp-server'

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