Skip to main content
Glama

Krate

Open a Krate result

fetch
Read-only

One Krate app or Krate's guide in full, by the id a result carries: an app's details and permissions in plain words, or the whole guide to making an app.

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": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA result's id, an app's link, or krate-guide

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
textYes
titleYes
metadataNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/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 that the call returns a full object (whole guide or app details plus permissions), which is modest added value. It says nothing about failure modes for an invalid or stale id, or how large the returned guide may be.

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?

One compact sentence with no filler; the input (id from a result) is front-loaded ahead of the return description. Slight deduction because the fragmentary grammar and the trailing 'the whole guide to making an app' phrase cost a little immediate comprehension.

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 single-parameter, read-only lookup with a full input schema, an output schema, and clear annotations, the description covers what an agent needs to call it: what the id is and what kind of object comes back. The only meaningful gap is the lack of routing guidance against similarly named sibling retrieval tools.

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 100% and the schema already states the id may be a result id, an app link, or the literal 'krate-guide'. The description only restates the result-id case, adding no syntax, format, or disambiguation details beyond the schema. Baseline 3 applies since the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource ('One Krate app or Krate's guide') and the accessor ('by the id a result carries'), and explains what comes back: app details and permissions, or the whole guide. However, it is written as a noun phrase with no explicit verb ('Open'/'Retrieve' appears only in the title), so the action is inferred rather than stated. It also does nothing to differentiate this from siblings like get_app and get_krate_guide, which by name suggest overlapping retrieval.

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 phrase 'by the id a result carries' implies the expected workflow: take an id out of a search result and open it. That is real implied guidance but it is never spelled out, and there is no statement of when to prefer this over the other retrieval tools, nor any exclusion or precondition.

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.