Skip to main content
Glama
Sign In
Gameball MCP Server

Gameball MCP Server

by Ahmedelmonady
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Docs: Search Docs

docs-search-docs

Search Gameball docs to locate relevant sections and snippets. Use when topic lookup fails or you need targeted results within a specific section.

Instructions

Full-text search across all Gameball docs. Returns titles and snippets. Use when docs-lookup-topic did not find what you need or you need to search within a specific section.

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": {
      "query": "<query>"
    },
    "name": "docs-search-docs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 5)
queryYesSearch query
sectionNoFilter by section: API Reference, Tutorials, Installation Guide, etc.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the return format (titles and snippets) and full-text behavior, but does not mention any limitations, authentication needs, or the nature of the search (e.g., ranking, exact match). For a read-only search tool, this is adequate but not rich.

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 short, front-loaded sentences. The main purpose is stated first, followed by clear usage guidance. No wasted words.

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?

Even without an output schema, the description explains the return content (titles and snippets). With 3 well-documented parameters and explicit usage guidance, the description is complete enough for a search tool. It could mention result ordering or limits, but it is not necessary.

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 all parameters. The description adds minimal meaning beyond saying you can search within a section, which aligns with the `section` parameter. Baseline 3 is appropriate.

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 this is a full-text search across all Gameball docs, returning titles and snippets. It differentiates itself from the sibling `docs-lookup-topic` by explicitly mentioning that use case.

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

Usage Guidelines5/5

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

Explicitly provides when-to-use guidance: 'Use when docs-lookup-topic did not find what you need or you need to search within a specific section.' This directly instructs the agent on selecting this tool over alternatives.

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