AI Worlds CLI Knowledge

Find CLI Configuration

worlds_get_cli_configuration

Read-onlyIdempotent

Search configuration keys and environment-variable names for one CLI. Returns public schema metadata and source links, never local values.

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

Input Schema

Name	Required	Description	Default
`limit`	No
`query`	No
`offset`	No
`include`	No		both
`product`	Yes
`availability`	No	Evidence labels: runtime-confirmed = shown by the installed release's own help; docs-confirmed = in official documentation or the published schema only; source-preview = in public source HEAD that no released version is tied to (no matching release tag); conditional = present only under a documented condition such as a provider, platform, login, or feature gate, or subject to a recorded drift note; historical = removed or retired.

Output Schema

Name	Required	Description	Default
`count`	Yes
`items`	Yes
`query`	Yes
`total`	Yes
`offset`	Yes
`product`	Yes
`has_more`	Yes
`next_offset`	No
`reference_url`	Yes
`release_version`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 4, 2026

addedInput schema / properties / availability / description

Added value: +"Evidence labels: runtime-confirmed = shown by the installed release's own help; docs-confirmed = in official documentation or the published schema only; source-preview = in public source HEAD that no released version is tied to (no matching release tag); conditional = present only under a documented condition such as a provider, platform, login, or feature gate, or subject to a recorded drift note; historical = removed or retired."

First observedAug 1, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds real value by disclosing that results are public schema metadata plus source links and never local values — a privacy/scope guarantee an agent could not derive from annotations. It omits pagination behavior and how the availability evidence labels affect results.

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 tight sentences with no filler, and the positive statement of purpose is front-loaded ahead of the negative scope constraint. Every clause carries information.

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-value detail is not required, and the description does note the return shape anyway. However, for a six-parameter search tool with very low schema coverage and a non-obvious evidence-label filter, the description leaves pagination, result ordering, and evidence filtering unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17%, so the description needs to compensate and largely does not. It implies the product scoping and loosely gestures at the include enum via 'configuration keys and environment-variable names', but query, limit, offset, and availability receive no explanation of matching behavior, ranking, or paging semantics beyond the enum text already in the schema.

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 configuration keys and environment-variable names, scoped to one CLI. That is narrow enough to distinguish it from the broader worlds_search_cli_reference, but the description never names or contrasts that sibling, so routing is inferred rather than stated.

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: the agent can infer this is the tool for config-key/env-var lookups per product. The phrase 'never local values' functions as a scope exclusion, but there is no explicit when-to-use, when-not, or pointer to an alternative such as worlds_search_cli_reference or worlds_get_cli_command.

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

All AI Worlds CLI Knowledge 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.