Skip to main content
Glama
AccelByte

AGS Extend SDK MCP Server

Official
by AccelByte
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Search symbols

search-symbols

Search for AccelByte Gaming Services SDK symbols by name, tags, or description using fuzzy matching to find functions and models for code generation.

Instructions

Search for symbols by name, tags, or description with fuzzy matching support.

Usage Patterns:

  • search_symbols(query: "auth") → finds auth-related symbols (paginated)

  • search_symbols(query: "create, user") → finds user creation symbols (paginated)

  • search_symbols(query: "") → returns all symbols (paginated)

  • search_symbols(query: "stats", symbolType: "function") → finds stats-related function symbols (paginated)

  • search_symbols(query: "stats", symbolType: "model") → finds stats-related model symbols (paginated)

  • search_symbols(query: "", symbolType: "function") → returns all function symbols (paginated)

  • search_symbols(query: "", symbolType: "model") → returns all model symbols (paginated)

Recommended Workflow:

  1. Search: search_symbols(query: "user creation") → get the IDs of the symbols that match the query and other symbols that are referenced by the matched symbols.

  2. Describe: describe_symbols( ids: [ "CreateUser@iam.function", "CreateUserRequest@iam.model", "CreateUserResponse@iam.model" ] )

  3. Analyze: Use the symbol's description, imports, example, fields, parameters, and return_type for instantiation and usage information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch terms for symbols (empty string returns all symbols).
limitNoMaximum number of symbols to return (default: 25).
offsetNoOffset for pagination (default: 0).
symbolTypeNoType of symbols to return (default: null, meaning all types).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYesRepresents a paginated list of symbol summaries.

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behaviors: it mentions fuzzy matching support, pagination (implied through usage patterns), and provides a complete workflow context. However, it doesn't explicitly mention rate limits, authentication needs, or error conditions, keeping it from 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.

Conciseness4/5

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

The description is well-structured with clear sections (description, usage patterns, recommended workflow) and every sentence adds value. However, the usage patterns section is quite lengthy with 7 examples, which could be more concise while still being informative.

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?

Given the tool has an output schema (mentioned in context signals) and 100% schema coverage, the description provides excellent context. It covers purpose, usage guidelines, behavioral aspects, and integrates with sibling tools, making it complete for a search tool with good structured data support.

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 description coverage is 100%, so the baseline is 3. The description adds value through usage patterns that illustrate how parameters interact (e.g., combining query with symbolType), but doesn't provide additional semantic details beyond what's already in the schema descriptions.

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 clearly states the tool searches for symbols by name, tags, or description with fuzzy matching support. It specifies the exact resource (symbols) and method (search with fuzzy matching), and distinguishes it from the sibling describe-symbols tool by focusing on search rather than detailed description.

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 'Recommended Workflow' section explicitly outlines when to use this tool (step 1: search) versus the sibling describe-symbols tool (step 2: describe), providing clear alternatives and context. It also includes multiple usage patterns that demonstrate different scenarios for using the tool.

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/AccelByte/ags-extend-sdk-mcp-server'

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