Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

search_app_directory

Read-only

Search Discord's application directory by query, category, locale, or server to find apps matching specific criteria and filters.

Instructions

Search Applications Directory. [GET /application-directory-static/search]

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_app_directory"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNopage
queryNoSearch text
localeNolocale
sourceNosource
guild_idNoServer (guild) ID
page_sizeNopage size
category_idNocategory id
exclude_non_embedded_appsNoexclude non embedded apps
min_user_install_command_countNomin user install command count
exclude_apps_with_custom_install_urlNoexclude apps with custom install url
exclude_embedded_apps_without_primary_entry_point_app_commandNoexclude embedded apps without primary entry point app command

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only the HTTP endpoint, with nothing about pagination behavior, result caps, or what filters are combined with (AND/OR semantics) despite 11 optional parameters.

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?

Two short fragments with zero filler and the purpose front-loaded. It is efficient but borderline under-specified rather than verbose.

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

Completeness3/5

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

With 11 optional parameters, a read-only annotation set, and no output schema, the schema documents the individual knobs but the description does not explain default paging, result shape, or how the exclusion flags affect results. Adequate as a minimum-viable definition, but thin for a search tool with this many filters.

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 every parameter already carries its own description and the baseline of 3 applies. The description contributes no additional meaning about interaction between filters such as guild_id, source, and the exclude_* flags.

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

Purpose4/5

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

The description states a specific verb and resource ("Search Applications Directory") plus the underlying endpoint, so the agent can tell it queries the app directory. It does not distinguish itself from the closely named sibling search_directory_entries, leaving ambiguity about which index is searched.

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?

There is no guidance on when to use this tool versus alternatives such as search_directory_entries or list_app_directory_categories, and no statement of preconditions. The agent must infer usage purely from the name and endpoint path.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools