Kepler OGame Bot

get_function

Get one function of the Kepler scripting reference: signature, how many values it returns, its category, its examples, and whether it is in a published bot build yet ("availability").

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": {
      "name": "<name>"
    },
    "name": "get_function"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	Exact function name, for example "SendDiscordFile". Case is ignored.
`language`	No	Language of the reference: "en" (default) or "fr".

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries full behavioral burden; it does disclose the shape of the returned data (including what "availability" means), which is valuable without an output schema. It says nothing about behavior when the name is not found, error handling, or whether results are cached/static, leaving real gaps.

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 sentence with the resource stated first and the returned fields listed compactly. Slightly dense parenthetical quoting of "availability" but 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?

For a two-parameter read lookup with no annotations and no output schema, the description does the important work of enumerating return fields. Only the failure/not-found behavior is missing, which is a minor but real omission.

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%, and the schema already documents the name parameter (including case-insensitivity) and the en/fr language option. The description adds no parameter-level meaning beyond it, so baseline 3 applies.

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?

The description gives a specific verb and resource ("Get one function") and enumerates exactly what is retrieved: signature, return count, category, examples, and availability. It conveys single-item lookup, which contrasts with siblings like list_category and search_functions, but never names those alternatives explicitly.

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 by "Get one function" versus a plural search/list pattern; there is no explicit statement of when to use this over search_functions or what to do when the exact name is unknown. An agent can infer intent but receives no routing guidance.

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 tools Inspect

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.