Create a Timer node with configurable wait time, one-shot mode, and autostart for managing timed events.
Create a Timer node with configuration
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Optional timer node name | |
| oneShot | No | One-shot mode. Default: false | |
| waitTime | No | Timer duration in seconds. Default: 1.0 | |
| autostart | No | Auto-start the timer. Default: false | |
| parentPath | No | Parent node path. Default: "/root" |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. However, it does not mention any side effects, permissions, or changes beyond what is in the input schema. Minimal information.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence with no unnecessary words. It is front-loaded and to the point.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has 5 parameters, no required ones, and no output schema. The description is minimal but covers the basic purpose. However, it does not explain return values or how the node is attached to the scene tree.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description 'with configuration' adds no additional meaning to the parameters beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'Create' and resource 'Timer node'. It is specific and directly explains what the tool does, but it does not differentiate from other 'create' sibling tools like game_create_animation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidelines on when to use or when not to use this tool. The usage is implied from the name and description, but there is no mention of alternatives or conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/tugcantopaloglu/godot-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server