Skip to main content
Glama
Sign In

Kepler OGame Bot

by net.keplerbot
OverviewDiscussionsAdmin

search_functions

Search the Kepler scripting reference by name or summary. Returns matching function names with their signature and the number of values they return. An entry carrying a "since" field is not in every build; an empty one is documented but not published yet.

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

Input Schema

NameRequiredDescriptionDefault
queryYesText to look for in the function name and summary.
languageNoLanguage of the reference: "en" (default) or "fr".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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. It does useful work by disclosing the result shape and the semantics of the "since" field (absent from some builds) and an empty value (documented but unpublished), but it says nothing about result limits, pagination, ordering, or match behavior.

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?

Three short sentences, front-loaded with purpose and return shape, then the field-semantics caveat. The "since" note is niche but earns its place because it prevents misreading results; no filler.

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?

With no output schema, the description steps in to describe the return values and their edge cases, which is exactly what an agent needs. The remaining gaps (result caps, ordering) are minor for a simple two-parameter lookup tool.

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%, so both parameters are already documented in the schema. The description adds only that the query matches against name and summary, which is a marginal clarification rather than new syntax or constraint detail.

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 and resource ("Search the Kepler scripting reference") and even summarizes the return payload (matching names, signature, return-value count). It does not explicitly contrast itself with the sibling get_function, so an agent must infer that search is for discovery and get_function for retrieval of a single known item.

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?

The description implies the discovery use case (look up functions by name or summary text) but never states when to prefer it over get_function or list_category, nor any preconditions. Usage is inferable from the verb, not spelled out.

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

All Kepler OGame Bot toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources