Skip to main content
Glama
AccelByte

AGS Extend SDK MCP Server

Official
by AccelByte
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Hybrid

Search symbols

search-symbols

Search for AGS Extend SDK symbols by name, tags, or description using fuzzy matching. Returns paginated results filtered by symbol type (function or model) 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
limitNoMaximum number of symbols to return (default: 25).
queryYesSearch terms for symbols (empty string returns all symbols).
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.6/5.0
Behavior4/5

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

Despite no annotations, the description discloses pagination behavior, fuzzy matching, and default values. It doesn't state read-only explicitly but is implied by the context. Leaves some room for more explicit safety cues.

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?

Well-structured with sections and front-loaded purpose. However, the multiple example patterns could be condensed without losing clarity.

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?

Covers all key usage aspects: search functionality, pagination, filtering, and workflow integration with sibling tool. Output schema exists, so no need to detail return values.

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?

With 100% schema coverage, baseline is 3. The description adds numerous concrete examples demonstrating how parameters like query and symbolType behave, and clarifies syntax (e.g., comma-separated queries).

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 'Search for symbols by name, tags, or description with fuzzy matching support,' specifying the verb, resource, and distinguishing from the sibling tool 'describe-symbols'.

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?

Provides explicit usage patterns and a recommended workflow that links this tool to its sibling, showing when to use search and when to use describe. It also implies alternatives.

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