Skip to main content
Glama

get_site_statistics

Retrieve AniList site statistics, including trends and metrics, from the last seven days to analyze user activity and platform usage.

Instructions

Get AniList site statistics over the last seven days

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • tools/misc.ts:116-143 (registration)
    Registers the 'get_site_statistics' MCP tool with an inline handler that fetches and returns AniList site statistics over the last seven days as JSON text, handling errors appropriately.
    server.tool(
      "get_site_statistics",
      "Get AniList site statistics over the last seven days",
      {},
      {
        title: "Get Site Statistics",
        readOnlyHint: true,
        openWorldHint: true,
      },
      async () => {
        try {
          const statistics = await anilist.siteStatistics();
          return {
            content: [
              {
                type: "text",
                text: JSON.stringify(statistics, null, 2),
              },
            ],
          };
        } catch (error: any) {
          return {
            content: [{ type: "text", text: `Error: ${error.message}` }],
            isError: true,
          };
        }
      },
    );
  • The handler function for the 'get_site_statistics' tool, which calls anilist.siteStatistics() and formats the response.
    async () => {
      try {
        const statistics = await anilist.siteStatistics();
        return {
          content: [
            {
              type: "text",
              text: JSON.stringify(statistics, null, 2),
            },
          ],
        };
      } catch (error: any) {
        return {
          content: [{ type: "text", text: `Error: ${error.message}` }],
          isError: true,
        };
      }
    },
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool retrieves statistics but doesn't disclose behavioral traits like whether it's a read-only operation, requires authentication, has rate limits, or what format the statistics are returned in. The description is minimal and lacks necessary context for safe invocation.

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, efficient sentence that front-loads the core purpose without unnecessary words. Every part of the sentence contributes meaning: the action, resource, and temporal scope. It's appropriately sized for a simple tool.

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 has no parameters and no output schema, the description is minimally complete but lacks details about return values or behavioral context. For a statistics retrieval tool, users need to know what data is returned and in what format. The description doesn't compensate for the absence of annotations or output schema.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, maintaining focus on the tool's purpose without redundancy. This meets the baseline for zero-parameter tools.

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 verb 'Get' and the resource 'AniList site statistics', specifying the scope 'over the last seven days'. It distinguishes itself from siblings like get_user_stats or get_activity by focusing on site-wide data rather than user-specific information, though it doesn't explicitly name alternatives.

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?

The description implies usage for retrieving aggregated site statistics from the past week, but doesn't provide explicit guidance on when to use this tool versus alternatives like get_user_stats or get_genres. It lacks statements about when not to use it or detailed context for selection.

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

Related 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/yuna0x0/anilist-mcp'

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