Skip to main content
Glama
Sign In

krobot

by io.github.Kromatic-Innovation
OverviewDiscussionsAdmin

List resources

list_resources
Read-onlyIdempotent

Browse what Kromatic has when the user wants to see the options rather than answer a specific question: every downloadable template, the method pages of The Real Startup Book, Kromatic's other MCP servers (Fermi for estimates, Neumann for Monte Carlo simulation) or the agent skills list.

Call it with {} for an overview of every group with counts and examples, or filter to page through one group, e.g. {"resource_types": ["Download"]}, {"resource_types": ["Book Section"]}, {"resource_types": ["MCP Server"]}, {"resource_types": ["Skill"]}. Returns titles, ids, kromatic.com urls and types, not the content. No sign-in needed.

Next: pass next_cursor back as cursor for the next page, or call read_resource with an item's id.

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

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page when filtering, 1 to 100 (default 50).
cursorNoThe next_cursor from the previous response. Omit for the first page.
source_keysNoOptional. Only these sources: real_startup_book (method pages), blog_content (Kromatic blog), learning_library (courses, lessons, templates, and the MCP Server and Skill entries), tools_and_games.
resource_typesNoOptional. Only these types. Leave both filters empty for the overview. 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.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful facts beyond that: no sign-in required, results contain titles/ids/urls/types but not the content itself, and pagination flows through next_cursor. It does not describe result ordering or what the overview counts cover, so a 3 rather than higher.

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?

The opening sentence front-loads purpose and the follow-up guidance closes the loop; nothing is padded prose. The run of four near-identical filter examples is mildly repetitive and could be compressed, but each illustrates a real enum group.

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 zero-required-parameter, read-only listing tool with annotations covering safety and no output schema, the description supplies everything an agent needs: what comes back, what does not (content), the overview-vs-filter switch, pagination, and the natural next call.

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; the description earns a bump by giving worked examples of resource_types values and by stating the paging contract (pass next_cursor back as cursor). It stays consistent with the schema's note that both filters empty yields the overview rather than adding new semantics for source_keys or limit.

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 — browsing every downloadable template, book method page, MCP server and skill entry Kromatic exposes — and frames the scope as 'see the options rather than answer a specific question', which separates it from a search-style sibling. The overview-versus-filter behavior is spelled out in the same breath.

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

Usage Guidelines4/5

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

Gives clear when-to-use context ('browse' vs answering a specific question) and concrete invocation examples with {} and each filter value. It also names the follow-up path (read_resource, or pass next_cursor back). It stops short of naming search_resources as the explicit alternative for targeted lookups, leaving that only implied.

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