Skip to main content
Glama
Paillat-dev

topgg-mcp

by Paillat-dev
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

post_metrics

Submit metrics including server count, shard count, or member count to update your Top.gg project.

Instructions

Submit a metrics payload for the current Top.gg project. Provide the fields relevant to your project type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectNoName of the configured project to target (e.g. "mybot" for TOPGG_TOKEN_MYBOT). Required when multiple tokens are configured; omit when only one is configured.
shard_countNoDiscord bot: shards.
member_countNoDiscord server: members.
online_countNoDiscord server: online members.
player_countNoRoblox game: current players.
server_countNoDiscord bot: servers.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed17 schema fields changedv0.0.4
    • changedInput schema / properties / member_count / description
      Previous value: -"Discord server: member count."New value: +"Discord server: members."
    • changedInput schema / properties / member_count / minimum
      Previous value: --9007199254740991New value: +0
    • changedInput schema / properties / online_count / description
      Previous value: -"Discord server: online member count."New value: +"Discord server: online members."
    • changedInput schema / properties / online_count / minimum
      Previous value: --9007199254740991New value: +0
    • changedInput schema / properties / player_count / description
      Previous value: -"Roblox game: player count."New value: +"Roblox game: current players."
    • changedInput schema / properties / player_count / minimum
      Previous value: --9007199254740991New value: +0
    • removedInput schema / properties / players_max
      Removed value: -{
-  "description": "Minecraft: max player slots.",
-  "maximum": 9007199254740991,
-  "minimum": -9007199254740991,
-  "type": "integer"
-}
    • removedInput schema / properties / players_online
      Removed value: -{
-  "description": "Minecraft: players online.",
-  "maximum": 9007199254740991,
-  "minimum": -9007199254740991,
-  "type": "integer"
-}
    • changedInput schema / properties / server_count / description
      Previous value: -"Discord bot: number of servers."New value: +"Discord bot: servers."
    • changedInput schema / properties / server_count / minimum
      Previous value: --9007199254740991New value: +0
    • changedInput schema / properties / shard_count / description
      Previous value: -"Discord bot: number of shards."New value: +"Discord bot: shards."
    • changedInput schema / properties / shard_count / minimum
      Previous value: --9007199254740991New value: +0
    • removedInput schema / properties / tick_duration_avg
      Removed value: -{
-  "description": "Minecraft: average tick duration.",
-  "type": "number"
-}
    • removedInput schema / properties / tick_rate
      Removed value: -{
-  "description": "Minecraft: tick rate.",
-  "type": "number"
-}
    • removedInput schema / properties / uptime_seconds
      Removed value: -{
-  "description": "Minecraft: server uptime in seconds.",
-  "type": "number"
-}
    • removedInput schema / properties / world_size_x
      Removed value: -{
-  "description": "Minecraft: world size X.",
-  "type": "number"
-}
    • removedInput schema / properties / world_size_y
      Removed value: -{
-  "description": "Minecraft: world size Y.",
-  "type": "number"
-}
  2. First observedv0.0.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description must disclose behavioral traits. It only states that the tool submits metrics, but omits details about authorization, idempotency, rate limits, side effects, or error handling common to mutation tools.

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?

Two sentences with no wasted words. The action is front-loaded, and the second sentence provides contextual guidance. Ideal conciseness for a straightforward 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 absence of output schema and annotations, the description is adequate for a simple metric submission but lacks context on expected return values, confirmation messages, or how it relates to the batch sibling and other tools.

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%, so the schema already documents each parameter. The description adds a helpful directive to select relevant fields per project type, which provides some additional context beyond the schema, but does not explain parameter relationships or constraints.

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 states 'Submit a metrics payload for the current Top.gg project', clearly indicating the action (submit) and resource (metrics for a Top.gg project). The name 'post_metrics' and the sibling 'post_metrics_batch' imply differentiation, but the description does not explicitly distinguish between them.

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 says 'Provide the fields relevant to your project type,' which gives some guidance on parameter selection, but it does not explain when to use this tool versus alternatives like 'post_metrics_batch', nor does it include when-not or prerequisites.

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/Paillat-dev/topgg-mcp'

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