Skip to main content
Glama

Krate

Read the Krate app guide

get_krate_guide
Read-only

Krate's reference for writing a Krate app (a native app for Windows, macOS and Linux that also opens in a browser): the files an app is made of (Cargo.toml, src/lib.rs, manifest.toml), the API it may use, the permissions it may declare, the mistakes that fail a first build, and worked examples. No sign-in needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
nextYes
charactersYesThe guide's length; the guide itself is the text content

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, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: authentication needs are stated ('No sign-in needed'), the platform scope is defined, and the topics the guide covers are listed so the agent knows what it will get back.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence: purpose first, then a parenthetical scope definition, then a compact list of covered topics, then the auth note. No filler, and every listed item contributes information an agent could act on.

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?

With zero parameters and an output schema present, the description needn't explain return values, and it still outlines the guide's content. What remains unstated is when in a workflow to consult it relative to build_app or get_app, a minor gap for a documentation tool.

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 nothing for the description to disambiguate. The baseline of 4 applies; no parameter-level detail is expected or missing.

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 names a specific resource (a reference guide for writing a Krate app) and enumerates its contents — build files, API, permissions, common build failures, examples. That makes it clearly distinct from siblings like build_app or get_app, though it never explicitly contrasts itself with them.

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 mention of 'the mistakes that fail a first build' hints the agent should read this before building, but there is no explicit 'use this when' clause and no alternative named. An agent can infer the trigger, but must infer it.

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.