Skip to main content
Glama
BRNDMK

brandomica-mcp-server

App Store Search

brandomica_check_appstores
Read-onlyIdempotent

Search iOS App Store and Google Play to verify brand name availability for mobile apps. Check if apps with your brand name already exist on major app platforms.

Instructions

Search iOS App Store and Google Play for apps matching the brand name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brand_nameYesThe brand name to check

Implementation Reference

  • The handler for 'brandomica_check_appstores' which calls the API and formats the result.
      "brandomica_check_appstores",
      {
        title: "App Store Search",
        description:
          "Search iOS App Store and Google Play for apps matching the brand name.",
        inputSchema: z.object(brandNameInput).strict(),
        annotations: toolAnnotations,
      },
      async ({ brand_name }) => {
        const data = (await fetchApi("check-appstores", brand_name)) as {
          results: AppStoreResult[];
        };
        return {
          content: [{ type: "text" as const, text: formatAppStores(data) }],
        };
      }
    );
Behavior4/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering safety and idempotency. The description adds useful context by specifying the search scope (iOS App Store and Google Play), which isn't captured in annotations. No contradictions with annotations exist.

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

Conciseness5/5

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

The description is a single, efficient sentence with zero wasted words, front-loading the core action and resources. Every element ('Search iOS App Store and Google Play for apps matching the brand name') directly contributes to understanding the tool's purpose.

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 search tool with one parameter, full schema coverage, and annotations covering safety and behavior, the description is largely complete. However, without an output schema, it could benefit from hinting at return types (e.g., app listings or matches), though the context is sufficient given the tool's straightforward nature.

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%, with the parameter 'brand_name' fully documented in the schema. The description adds no additional parameter details beyond implying it's used for matching in app stores, which aligns with but doesn't extend the schema. Baseline 3 is appropriate given high schema coverage.

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 specific action ('Search') and resources ('iOS App Store and Google Play for apps matching the brand name'), distinguishing it from sibling tools like brandomica_check_domains or brandomica_check_social that search different platforms. It precisely communicates the tool's function without redundancy.

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

Usage Guidelines3/5

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

The description implies usage when searching app stores for brand-related apps, but lacks explicit guidance on when to use this tool versus alternatives like brandomica_check_all or brandomica_batch_check. It provides basic context but no exclusions or comparisons to sibling tools.

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/BRNDMK/brandomica-mcp-server'

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