Skip to main content
Glama

search_code_examples

Search for game development code examples by describing your specific implementation challenge. Retrieve tested snippets from a vector database covering mechanics, rendering, physics, AI, and more.

Instructions

Searches and retrieves relevant game development code examples from a vector database based on specific game development requirements or programming challenges. This tool performs semantic search to find code snippets and examples that match the user's game development needs. It analyzes both the user message and associated tags to identify the most appropriate game code examples from the database. [WHEN TO USE THIS TOOL] You should use this tool whenever the user asks about game implementation details, game programming patterns, specific game feature implementations, or requests examples of how to implement something in game development. USE THIS TOOL if the user mentions specific game programming tasks, asks "how do I code X in my game", or needs reference implementations for game mechanics, rendering, physics, AI, or other game-specific systems. The results are returned in a structured format containing game client code, game server code, and descriptive explanations when available. The userMessage parameter should include detailed context about the game programming challenge or implementation requirement, while the tags parameter should specify relevant game engines, frameworks, or concepts to narrow the search scope. Note: This tool does not generate complete games but rather provides existing code snippets and examples that address specific game implementation challenges. The quality of search results heavily depends on the clarity and specificity of the provided user message and tags. Examples typically demonstrate solutions to common game implementation problems and can be used as reference material for your own game development work. Common scenarios where this tool is useful include: 1) When a user asks "How do I implement character movement in Unity?", 2) When they need examples of game state management for specific operations, 3) When they want to see how others have implemented a specific game UI component, 4) When they need patterns for game networking, 5) When they request code for handling specific game physics edge cases. IMPORTANT: You should proactively offer to search for game code examples whenever a user is discussing game implementation details or asking how to build something in a game, even if they don't explicitly request examples. Always prefer showing existing, tested game code examples over generating new code when possible. If you are uncertain whether relevant game code examples exist for a user's question, it is better to use this tool and check rather than assume none are available. Even partial matches can provide valuable game implementation insights to users.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagsYesAn array of specific keywords, game engines, frameworks, or game programming concepts that help narrow down the search. ALL TAGS MUST BE IN ENGLISH ONLY. Always include both general game technology categories (e.g., "Unity", "Unreal Engine") AND specific game concepts (e.g., "character controller", "collision detection") relevant to the query. If the user mentions any game technologies, ALWAYS include them as tags. Commonly useful tags include: "Unity", "Unreal Engine", "Godot", "Phaser", "game physics", "game AI", "pathfinding", "animation", "game networking", "procedural generation", "particle systems", "game UI", "state management", "input handling", etc. Each tag should be a string that precisely identifies a game technology (e.g., "Unity", "Unreal Engine", "WebGL"), a game programming concept (e.g., "physics", "AI", "rendering"), or a specific game feature (e.g., "character controller", "inventory system", "dialog system"). Tags are used to filter the vector database search and improve the relevance of returned game examples. Include both broad and specific tags to ensure comprehensive results.
userMessageYesA detailed description of the game programming problem or implementation challenge that requires code examples. THIS MUST BE PROVIDED IN ENGLISH ONLY. Extract the core game implementation requirements from the user's query, focusing on what they're trying to build or implement in their game. This should include context about what the user is trying to accomplish, specific technical requirements, game engines or technologies being used, and any constraints or edge cases that need to be addressed. The more specific and detailed this description is, the more relevant the returned game code examples will be. Examples of good messages include explaining a complex game mechanic integration, describing a game UI component behavior, detailing a game physics simulation, or requesting help with game AI implementation.
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure and does a strong job. It discloses limitations ('does not generate complete games'), output format ('structured format containing game client code, game server code, and descriptive explanations'), and factors affecting quality (clarity of userMessage and tags). Minor omissions like rate limits or error behavior prevent a perfect score.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is overly verbose and repetitive, with redundant statements about when to use the tool and the importance of search quality. While it is structured with sections, many sentences do not earn their place, making it less concise than ideal.

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

Completeness5/5

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

With no output schema and no sibling tools, the description provides comprehensive context: it explains return format, limitations, scenarios, and proactive usage. It covers both what the tool does and how to best leverage it, making it contextually complete for a search tool.

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?

The input schema already provides 100% coverage with detailed descriptions for both parameters, including usage guidance and examples. The description briefly reiterates that userMessage should be detailed and tags should narrow scope, but adds marginal semantic value beyond the schema. Per the baseline for high schema coverage, 3 is appropriate.

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?

The description explicitly states the tool 'searches and retrieves relevant game development code examples from a vector database' with a specific verb and resource. It clarifies the semantic search nature and the type of content returned, leaving no ambiguity about purpose.

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

Usage Guidelines5/5

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

The description includes an explicit '[WHEN TO USE THIS TOOL]' section with detailed scenarios, specific examples, and proactive guidance to search even when not explicitly requested. It clearly defines when to prefer this tool over generating new code, which is excellent usage guidance.

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/longfin/mcp-agent8-o'

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