Skip to main content
Glama
Sign In
mcp-server-runescape

mcp-server-runescape

by stjepko-xyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_player_count

Retrieve the current player count for RuneScape and Old School RuneScape to gauge live player activity.

Instructions

Returns the number of players currently online in RuneScape and Old School RuneScape.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations available, the description carries the full burden of behavioral disclosure. It honestly describes the core function (returning a count), but provides no additional context such as whether the count is live/cached, whether it covers all worlds, or any potential limitations. This is acceptable for a simple read-only tool, but leaves some ambiguity about 'currently online'.

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, front-loaded sentence that directly states the tool's purpose without any filler or repetition. Every word contributes to clarity, making it highly concise and well-structured.

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

Completeness5/5

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

For a tool with no parameters and no output schema, the description is fully complete. It clearly specifies what is returned (the number of players) and the domain (RuneScape and OSRS). No additional context is necessary for an agent to understand and correctly invoke this tool.

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 zero parameters and the schema is empty, so there is no parameter information to elaborate. The baseline for zero-parameter tools is 4, and the description adds sufficient context by explaining what the output represents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function with a specific verb ('Returns') and resource ('number of players currently online in RuneScape and Old School RuneScape'). It effectively distinguishes itself from sibling tools like get_item_details or get_player_hiscore, which focus on different data types.

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 explicit guidance on when to use this tool versus alternatives. It only states what it does, without suggesting scenarios (e.g., 'use this to check live player counts') or exclusions. The usage is not even clearly implied beyond the basic function.

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