Skip to main content
Glama

Get Project Info

get_project_info
Read-onlyIdempotent

Retrieve metadata about a Godot project by providing its project path, giving AI agents the project information they need to develop and test Godot 4 games autonomously.

Instructions

Retrieve metadata about a Godot proj…

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectPathYesGodot project path

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
dataNo
metaYes
errorNo
Behavior3/5

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

Annotations already indicate readOnlyHint=true and idempotentHint=true. Description adds no further behavioral details beyond the obvious 'Retrieve metadata'.

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?

Very short and to the point, but truncated (ends with '…'). No unnecessary words; however, the truncation reduces completeness.

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 simple read-only tool with one parameter and annotations covering safety, the description is adequate but could mention what specific metadata is returned, especially given the output schema exists.

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% and already describes projectPath as 'Godot project path'. Description does not add any extra meaning to the parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description uses clear verb 'Retrieve' and resource 'metadata about a Godot project'. It distinguishes well from sibling tools like get_godot_version or game_screenshot.

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?

No guidance on when to use this tool versus alternatives like get_godot_version or verify_project. No exclusions or contextual advice provided.

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/beremaran/godot-agent-loop'

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