Skip to main content
Glama
Sign In

krobot

by io.github.Kromatic-Innovation
OverviewDiscussionsAdmin

Download resource

download_resource
Read-only

Get the actual files of a Kromatic template or worksheet, such as the Pivot or Persevere template, when the user wants to fill it in or share it. Pass the item's id or the download's slug.

Needs a free Kromatic account. Just call it: if the user is not signed in, their AI app shows the Kromatic sign-in screen, where they can create the account, and then this same call goes through. Do not refuse or ask them to sign in first. If the app cannot show a sign-in screen, the call returns a "Sign in to use download_resource" error; tell the user this step needs a free Kromatic account. It changes nothing for the user; it only issues links. Returns each file's label, type, an is_example flag and a url. A paid file comes back with no url, access "requires_purchase" and the page_url where it is sold on kromatic.com.

Next: give the links to the user straight away. They stop working at expires_at. Each call issues fresh links and records them as issued; nothing else changes.

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

Input Schema

NameRequiredDescriptionDefault
idNoThe template's id from list_resources, search_resources or read_resource. A Download File id selects one file.
slugNoAlternative to id: the download's slug, e.g. pivot-or-persevere-template.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 idempotentHint=false, but the description goes further: sign-in requirements, the exact fallback error text, link expiry via expires_at, and paid-file behavior ('requires_purchase', page_url). The one nuance worth flagging is that each call 'records them as issued' — a server-side write-like effect that sits slightly at odds with a purely read-only framing, though it is not destructive and does not contradict the hints outright.

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 is front-loaded and the sign-in workflow is sequenced clearly with 'Next:' for the hand-off step. There is mild redundancy between 'It changes nothing for the user; it only issues links' and 'records them as issued; nothing else changes', which restate the same reassurance twice.

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 two-parameter download tool with no output schema, the description covers everything an agent needs: auth handling, failure recovery, return fields (label, type, is_example, url), expiry timing, and the paid-content path. Nothing material is left for the agent to infer.

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%, so both id and slug are already fully documented, including the 'Download File id selects one file' case. The description only restates 'Pass the item's id or the download's slug' without adding format, precedence, or error semantics beyond the schema. Baseline 3 applies.

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 — 'Get the actual files of a Kromatic template or worksheet' — and names concrete artifacts ('Pivot or Persevere template'). It implicitly separates itself from list_resources/search_resources/read_resource by emphasizing 'actual files' versus metadata lookup, though it never names those siblings directly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the trigger condition explicitly ('when the user wants to fill it in or share it') and pre-empts the most likely misstep with 'Do not refuse or ask them to sign in first. Just call it.' It also tells the agent what to do when the sign-in screen is unavailable, which is an unusual but real branching case.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All krobot toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources