Skip to main content
Glama
Sign In
Gameball MCP Server

Gameball MCP Server

by Ahmedelmonady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Docs: Get Doc Page

docs-get-doc

Fetches the full content of a specific documentation page by path, enabling you to read complete guides or API references after locating a topic.

Instructions

Get the full content of a specific doc page by path. Use after docs-lookup-topic when you need to read a specific page in full.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "<path>"
    },
    "name": "docs-get-doc"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesDocument path, e.g. "installation-guide/web/getting-started"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It implies a read operation ('Get the full content') but does not disclose response format, error behavior, or authentication/rate-limit requirements. It adds some context (full content, by path) but lacks richer behavioral detail.

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 two sentences with no wasted words. The first sentence states the essential function, and the second provides usage guidance. Every part earns its place.

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

Completeness4/5

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

For a simple one-parameter get tool, the description gives a clear purpose and usage workflow relative to sibling tools. However, without an output schema, it does not specify the exact return format beyond 'full content', which leaves some ambiguity.

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 coverage is 100% for the single parameter 'path', with a clear example provided. The description's mention of 'by path' is redundant with the schema, so it does not add significant meaning beyond what the schema already documents.

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 'Get the full content of a specific doc page by path' clearly identifies the verb (get), resource (doc page), and scope (by path). It also distinguishes from sibling tools by noting it should be used after docs-lookup-topic for reading a specific page in full.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage context: 'Use after docs-lookup-topic when you need to read a specific page in full.' This names the preceding tool and the condition, though it does not explicitly list exclusions or alternatives beyond that.

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