Skip to main content
Glama

APP NAVI

search_apps

APP NAVI のアプリを検索する。値が null の項目は「未確認」(推測していない)。Search indie/small-team apps; null means unverified.

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_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoキーワードまたはやりたいことの文(例: 現場で見積もりができるアプリ)。合う順に返す / keyword or what you want to do, ranked by relevance
ai_onlyNoAI を使っているものだけ
categoryNoカテゴリー slug(list_categories で取得)
free_onlyNo無料プランがあるものだけ
japanese_onlyNo日本語対応のものだけ

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"キーワード(アプリ名・機能・タグ)/ keyword"New value: +"キーワードまたはやりたいことの文(例: 現場で見積もりができるアプリ)。合う順に返す / keyword or what you want to do, ranked by relevance"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description has to carry the full behavioral burden, and it does disclose one meaningful trait: null fields mean 'unverified' rather than guessed, which shapes how an agent should interpret results. It says nothing about ranking, result size, pagination, or read-only/safety behavior, and it doesn't mention that it returns no matching results.

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 sentences with the core purpose front-loaded, followed by the null-semantics caveat. The Japanese/English mirroring is slightly redundant, but it is compact overall and contains no filler.

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?

Six optional parameters at high schema coverage and no output schema mean the description needs to explain result semantics; it does so partly by defining null as unverified. It omits how results are ordered, how many are returned, and how the search differs from browsing by category, leaving moderate gaps.

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 coverage is 83%, so the schema already explains query, category, and the boolean filters well. The description adds no meaning beyond that; 'null means unverified' concerns returned records, not input parameters, so the 100%-coverage baseline of 3 applies.

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 gives a specific verb and resource (search / apps) and adds scope that distinguishes it from search_developers: it covers 'indie/small-team apps'. It doesn't contrast itself with get_ranking, list_categories, or get_app, so differentiation is only partial.

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?

The description gives no guidance on when to use this tool instead of its siblings, and it doesn't explain when not to. The only pointer toward an alternative (use list_categories to get a category slug) lives in the input schema, not in the description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources