Skip to main content
Glama

Feature Library

Get a kit for a kind of build

get_kit
Read-only

Free. A tested set of parts for a kind of build (by kit id, or matched to the purpose in words), built on the foundations, with a tone applied when given: the parts with why, role, stack, needs and costs, the optional candidates, the glue you build yourself, what the library lacks, the tone’s settings and per-part knobs, and the looks that fit, at the level asked for (exact, tuned or inspired: what may change, what must stay); and the page shapes the purpose calls for (starting points for the page as a whole), or, when none fits, how to compose one.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "purpose": "<purpose>"
    },
    "name": "get_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
toneNoOptional tone id from the catalogue (e.g. strict, refined, playful).
levelNoHow closely the build follows a look: exact (the look as shipped; the dials and switches only, the default), tuned (also the look’s knobs, in range, then check_look) or inspired (your own look carrying its character; never its name).
purposeYesA kit id, or the kind of build in words, e.g. "a calm dashboard for finance".
platformNoOptional target platform for the costs shown, as for find_parts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds two things annotations do not: that the call is 'Free', and that the result may contain no page shape and instead explain how to compose one. It says nothing about what happens when the purpose matches no kit or how large the payload can be.

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

Conciseness2/5

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

The entire definition is a single run-on sentence of roughly 100 words chained with commas and colons, mixing inputs (kit id, purpose, tone, level) with an exhaustive list of outputs. 'Free.' is usefully front-loaded, but the remainder is dense enough that key facts, like the id-vs-words input, are buried mid-sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 carries the return-value burden and does so thoroughly by enumerating the sections of a kit. However, for a high-complexity discovery tool it leaves real gaps: no sibling differentiation, no failure behavior for an unmatched purpose, and no indication of result size or how tone interacts with missing parts.

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 only paraphrases what the schema already documents: purpose can be an id or words, tone is applied 'when given', and level controls 'what may change, what must stay'. The elaboration on exact/tuned/inspired adds modest semantics but does not exceed the enum descriptions.

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 the resource and then enumerates its contents concretely: the parts with why/role/stack/needs/costs, optional candidates, 'glue you build yourself', library gaps, tone settings, looks and page shapes. That is far more than a restatement of 'get_kit'. It never distinguishes the resource from siblings like get_recipe, get_playbook or get_shape, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance. Nothing tells the agent whether to call get_kit instead of get_recipe, get_playbook or get_brief for a build task, nor what prerequisites (e.g. a known kit id) exist. The only routing hint, 'then check_look', lives in the level enum in the schema rather than the description.

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