Skip to main content
Glama

Start here: learn the Okam Storefront Kit

kit_learn
Read-onlyIdempotent

Public: call first whenever you build or change a restaurant's own ordering website or table booking on Okam. Returns the must-nots (the server owns every price, payment is the guest's own act), the build steps, the sandbox key, the topics and, with framework, the scaffold plan. The kit gives logic and outcomes, never a look: design the site from the restaurant's brief. Not for ordering food as a guest or for restaurant admin. Example: {"framework":"vite-react"}. Next: kit_docs_get for the topics the steps name.

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

Input Schema

NameRequiredDescriptionDefault
frameworkNoFramework for the scaffold plan: next, astro, vite-react or html (read package.json). Pass it on the first call.
kitVersionNoOptional kit version you were told to use; the current kit is always served.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already establish that this is a safe, read-only, idempotent operation, and the description adds substantial domain behavior: the server owns prices, payment is the guest's act, the kit provides logic and outcomes but not visual design, and a sandbox key is included.

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?

The description is dense but front-loaded, starting with the primary call condition and then covering outputs, exclusions, example usage, and the next step. Every sentence carries relevant selection or usage 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?

There is no output schema, but the description explains the key returned elements: must-nots, build steps, sandbox key, topics, and optional scaffold plan. It also covers exclusions and follow-up tooling, making it complete enough for correct invocation.

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 description coverage is 100%, so the two parameters are already documented. The description adds an example framework value and notes that framework yields a scaffold plan, but it does not add much beyond the schema and does not mention kitVersion.

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?

The description states a specific action and resource: call this first when building or changing a restaurant's Okam ordering site or table booking. It clearly enumerates what the tool returns and distinguishes the tool from guest ordering and restaurant admin use.

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 gives an explicit trigger for use, says to call first, names excluded contexts, and points to kit_docs_get as the next tool for follow-up topics. This leaves little ambiguity about when to select 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.

Resources