krobot

Read resource

read_resource

Read-onlyIdempotent

Read a whole Kromatic page when an excerpt is not enough: a method's steps, thresholds, costs, examples and AI prompts, a blog post, a lesson, or what a template contains. Pass the id from list_resources or the document_external_key from search_resources.

Returns the title, the kromatic.com url, the full text and metadata. Templates are described and their files named, but never linked. It never triggers a sign-in screen: if part of an item is withheld, has_access is false and access says what is needed, "requires_sign_in" (read it again after the user has signed in; it may then need a purchase) or "requires_purchase", with an access_note giving the kromatic.com page.

Next: answer from the text and cite the url. Long pages come in parts: pass next_cursor back as cursor until it is null. For a template's files, call download_resource.

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

Input Schema

Name	Required	Description
`id`	No	An item id from list_resources or a document_external_key from search_resources; they are the same kind of id. Copy it exactly.
`slug`	No	Alternative to id: the item's slug, together with resource_type, e.g. slug "pivot-or-persevere-template" with resource_type "Download" for a template. Prefer the id when you have one.
`cursor`	No	The next_cursor from the previous read of this item, to get the next part.
`resource_type`	No	Needed with slug: the item's type as listed (templates are "Download"). Book Section = a method page of The Real Startup Book. Download = a template or worksheet; Download File = one file inside it. Tool = the full guide text for one of Kromatic's interactive web apps (e.g. Experiment Calculator, Startup Poker); Tools / Games = the website's link entry for the same apps, with less text. Prefer Tool when you want content.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 6, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well past the readOnly/idempotent/non-destructive annotations by disclosing partial-content behavior: has_access false, access values of 'requires_sign_in' or 'requires_purchase', an access_note pointing at the kromatic.com page, and the fact that re-reading after sign-in may still require a purchase. It also states that templates are described but their files are never linked, and that long pages are paginated.

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?

Front-loaded with the purpose, then parameters, return shape, and next steps in a logical order; the 'Next:' line is an efficient workflow cue. It runs long and the access-gating explanation is dense, but nearly every sentence carries decision-relevant information.

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?

With no output schema, the description still specifies the return fields (title, kromatic.com url, full text, metadata) and the access/has_access signaling, plus pagination via next_cursor. For a read tool with 4 optional parameters and gated content, that covers everything an agent needs to call it and interpret the result.

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 the baseline is 3. The description reinforces the id-origin rule and the cursor loop, but the enum meanings (Tool vs Tools / Games, Download vs Download File) and the slug+resource_type pairing are already carried by the schema, so little new semantic weight is added.

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

Purpose5/5

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

States a specific verb and resource (read a whole Kromatic page) and enumerates exactly what that covers: a method's steps, thresholds, costs, examples and AI prompts, a blog post, a lesson, or a template's contents. It explicitly contrasts with the excerpt path ('when an excerpt is not enough') and routes template files to download_resource, so an agent can separate it from search_resources and download_resource without opening any schema.

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?

Gives concrete entry conditions and alternatives: use it when an excerpt is insufficient, pass the id from list_resources or the document_external_key from search_resources, and call download_resource for a template's files. It also prescribes the follow-up workflow (answer from the text, cite the url, loop on next_cursor until null), leaving little to inference.

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

All krobot tools Inspect

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

Need Help?