Skip to main content
Glama

get_unread_count

Retrieve the total number of unread articles from your Tiny Tiny RSS feeds to monitor your reading backlog.

Instructions

获取当前未读文章总数

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler implementation and registration for 'get_unread_count' tool.
    server.tool(
      "get_unread_count",
      "获取当前未读文章总数",
      {},
      async () => {
        try {
          const count = await client.getUnread();
          return ok(`未读文章数: ${count}`);
        } catch (e: unknown) {
          return fail(`获取未读数失败: ${(e as Error).message}`);
        }
      },
    );
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states what the tool does ('获取当前未读文章总数') without explaining how it works—e.g., whether it counts across all feeds or specific categories, if it's cached or real-time, or what permissions are required. This leaves significant gaps in understanding its behavior.

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 a single, clear sentence: '获取当前未读文章总数'. It's front-loaded with the core purpose, has zero waste, and is appropriately sized for a simple tool with no parameters. Every word earns its place by directly conveying the tool's function.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally complete. It states the purpose but lacks context on usage, behavior, or output format. For a read-only tool with no parameters, this might suffice, but it doesn't fully compensate for the absence of annotations or output schema, leaving some ambiguity.

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

Parameters4/5

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

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate here. A baseline of 4 is given as it adequately handles the lack of parameters without introducing confusion.

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's purpose: '获取当前未读文章总数' (Get the current total number of unread articles). It specifies the verb '获取' (get) and resource '未读文章总数' (total unread articles). However, it doesn't explicitly differentiate from siblings like 'get_article' or 'search_articles', which focus on individual articles or searches rather than aggregate counts.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention scenarios like checking unread counts before fetching articles or how it relates to siblings such as 'get_article' or 'search_articles'. Without context, an agent might misuse it or overlook better options.

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/aooiuu/ttrss-mcp'

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