Skip to main content
Glama

get_wiki_stats

Retrieves whole-wiki statistics including note counts, link edges, domain breakdowns, and top hub notes to help you assess wiki structure and connectivity.

Instructions

Wiki 전체 통계 — 노트 수, link edges, 도메인, 상위 hub 노트.

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_wiki_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. Calling it '통계' (statistics) strongly implies a read-only, side-effect-free aggregate, and the listed categories tell the agent what dimensions exist. However, it never states read-only-ness explicitly, nor whether results are cached/live, how expensive the call is, or what the hub ranking is based on.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded clause with the scope first and an em-dash enumeration of contents; zero filler. It is slightly under-sized for a tool with no annotations, but nothing in it is redundant.

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?

An output schema exists, so return shapes need not be explained, and with no parameters the schema burden is nil. The description covers what categories of stats are produced, which is the main thing an agent needs. What remains missing is the read-only/aggregate behavioral note and any routing hint versus domain- or link-oriented siblings.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly spends its words on output content instead of inventing parameter guidance.

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?

States a specific verb+resource (wiki-wide statistics) and enumerates the content categories returned: note count, link edges, domains, top hub notes. An agent can immediately tell this is the aggregate/summary tool rather than a per-note reader. It does not explicitly contrast itself with list_domains, which overlaps on the 'domains' facet.

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?

Usage is only implied: '전체 통계' (whole-wiki statistics) signals an overview/orientation call, typically first in a session. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g., use list_domains for per-domain detail).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.