Skip to main content
Glama

Krate

Get a Krate app

get_app
Read-only

One public Krate app's details, from its link or id: what it does, what it is allowed to do in plain words, its versions, size, publisher and signature, its link and its browser link. Accepts a hub link (https://hub.krate.tech/a/..., /run/...), the app's own id (v followed by 11 hex characters), a short id, or a full hash. An app removed from the registry answers with its removal notice only.

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": {
      "id_or_link": "<id_or_link>"
    },
    "name": "get_app"
  }
}

Input Schema

NameRequiredDescriptionDefault
id_or_linkYesA Krate app link, or its id

Output Schema

NameRequiredDescriptionDefault
appNo
foundYes
noticeNoThe removal notice, when removed
messageNo
removedYesThe app was taken down from the registry

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 this a safe, closed, non-destructive read, so the description adds real value beyond them: it discloses the exact identifier forms accepted and the edge-case behavior that a delisted app returns only its removal notice. It does not mention authentication or rate limits, but for a public read that gap is minor.

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?

Purpose and identifier argument come first, followed by accepted formats and then the removed-app exception, which is good front-loading. The opening sentence is a long comma-chained enumeration of return fields, slightly dense, though each item is informative rather than filler.

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 one-parameter read tool with full annotation coverage and an output schema, the description covers identifier formats, scope, and the delisted-app edge case — everything needed to call it correctly. Return-value explanation is redundant with the output schema but causes no harm.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes well past the schema's terse 'A Krate app link, or its id'. It specifies the hub link shapes (https://hub.krate.tech/a/..., /run/...), the canonical id format (v plus 11 hex characters), short ids, and full hashes — concrete guidance an agent could not derive from the schema alone.

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 opens with a specific verb and resource — 'One public Krate app's details' — and enumerates what is returned (capabilities, versions, size, publisher, signature, links). It is clearly a single-record lookup, which implicitly contrasts with the list/search siblings. It stops short of naming a sibling (e.g. search_apps) for the find-then-fetch flow, so it is clear but not explicitly differentiated.

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 rather than stated: the reader gathers it is for fetching one already-known app by link or id, and that removed apps yield only a removal notice. There is no explicit when-to-use-vs-alternatives guidance, such as pointing to search or search_apps when the identifier is unknown. That is adequate but leaves routing partly 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.