Skip to main content
Glama
woohq

Godette

by woohq
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

get_autoloads

Retrieve all autoload singletons configured in a Godot project to manage global resources and persistent game objects.

Instructions

Get all autoload singletons configured in the project.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • src/tools/project-tools.ts:111-117 (handler)
    The MCP tool handler for "get_autoloads" which fetches autoloads from the index.
    handler: async (_ctx) => {
  const autoloads = index.getAutoloads();
  return makeTextResponse({
    data: autoloads,
    metadata: { source: "index" },
  });
},
  • src/index/unified-index.ts:237-239 (helper)
    The actual implementation logic that retrieves autoloads from the autoloadIndex.
    getAutoloads(): AutoloadRef[] {
  return this.autoloadIndex.all();
}
  • src/tools/project-tools.ts:107-110 (registration)
    The registration of the "get_autoloads" tool within the project tools collection.
    {
  name: "get_autoloads",
  description: "Get all autoload singletons configured in the project.",
  schema: {},

Tool Definition Quality

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states a read operation ('Get'), implying it's likely non-destructive, but doesn't disclose any behavioral traits such as permissions needed, rate limits, output format, or whether it returns live data versus cached configurations. This leaves significant gaps for agent understanding.

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 a single, efficient sentence that directly states the tool's purpose without any fluff or unnecessary details. It's front-loaded and wastes no words, making it easy to parse quickly.

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

Completeness2/5

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

Given the tool has no output schema and no annotations, the description is incomplete. It doesn't explain what 'autoload singletons' are in this context, what the return format looks like (e.g., list, object, JSON), or any error conditions. For a tool with zero structured metadata, more context is needed for effective agent use.

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

Parameters4/5

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

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add param info, but that's appropriate here. A baseline of 4 is applied as it adequately handles the lack of parameters without redundancy.

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 clearly states the verb 'Get' and the resource 'all autoload singletons configured in the project', making the purpose specific and understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_config', 'get_project_settings', or 'get_runtime_state', which also retrieve project information but target different resources.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. With many sibling 'get_' tools available (e.g., get_config, get_project_settings), there's no indication of context, prerequisites, or exclusions for selecting this specific tool over others.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/woohq/godette-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server