Skip to main content
Glama

Krate

Search Krate apps

search_apps
Read-only

Search the public Krate gallery for apps by words. Results are ranked by how well the words match the app's name, then its description and publisher. Each result has the app's link (opens in Krate), a link that opens it in a browser tab, what it is allowed to do in plain words, its size, and whether its publisher is verified and the app signed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_apps"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results, at most 20 (default 10)
queryYesWords to look for, e.g. "markdown editor"
categoryNoOnly apps on this shelf

Output Schema

NameRequiredDescriptionDefault
queryYes
resultsYes
categoryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the ranking order (name, then description, then publisher) and the shape of each result including plain-language permissions and publisher verification/signing.

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?

Front-loaded with the purpose in the first clause, then a second sentence that carries the ranking and result detail. It is efficient, though the enumerated result fields partially duplicate what the existing output schema already specifies.

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?

Three simple parameters, full schema coverage and an output schema mean the core is well covered; ranking behavior and result contents round it out. Minor gaps remain around whether results are exhaustive within the limit or paged, but nothing blocks a correct call.

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 all three parameters including the category enum are already documented, establishing the baseline of 3. The description adds some meaning about how the query string is matched (name first, then description, then publisher) but says nothing about limit or category behavior beyond the schema.

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?

States a specific verb and resource ('Search the public Krate gallery for apps') plus the input modality ('by words'), and the 'public gallery' scoping separates it from a single-app lookup like get_app. An agent can identify the operation without opening the schema.

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?

Usage is implied by the wording: this is the tool for finding apps by keyword in the public gallery. However, there is no explicit when-to-use or when-not guidance and no named alternative for other lookup modes (e.g. fetching a known app by id), which leaves the routing decision to inference.

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.