Skip to main content
Glama

Krate

Featured Krate apps

list_featured
Read-only

The Krate gallery's front shelves: the apps picked to start with, and the newest apps, each with its link, what it is allowed to do in plain words, its size and its publisher.

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": "list_featured"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
newestYes
start_hereYes
newest_labelYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is clear without the description. The description adds useful context about the curated sections and the fields returned, but does not add deeper behavioral details such as ordering, limits, or recency rules.

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?

It is a single front-loaded sentence that communicates the two curated groups and the per-app fields without obvious filler. The 'front shelves' framing is slightly colloquial, but it is compact and informative.

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?

For a no-parameter, read-only listing tool with an output schema and explicit safety annotations, this description is complete enough to call correctly. It explains what is listed and what each entry contains, and the output schema can carry the exact return shape.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to clarify. The schema is empty and fully covers the input surface; the description appropriately does not invent parameter behavior.

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 identifies a specific curated resource: the gallery's 'front shelves,' split into apps 'picked to start with' and 'the newest apps.' It is clearly a listing tool rather than a search or build tool, though the metaphor 'front shelves' makes it slightly less crisp than a direct verb+resource statement.

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 contents imply usage for browsing featured and newest apps, which gives an agent enough context to understand when this is relevant. However, it does not explicitly say when to use this instead of search_apps or get_app, and it offers no exclusions or routing guidance.

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.