Skip to main content
Glama

Brilliant Design (hosted)

Load Brilliant knowledge

get_knowledge
Read-onlyIdempotent

Use this when writing Blueprint rows for a Brilliant design: it loads Brilliant's Blueprint and design knowledge pages by key (blueprint/core, blueprint/layout, blueprint/paint, blueprint/text, design/foundations). Each key pulls in its prerequisites unless includeDependencies is false; all loads the whole tree page by page within the response budget.

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

Input Schema

NameRequiredDescriptionDefault
allNoLoad every page of the tree (the response budget defers the rest by name).
keysNoKnowledge keys, each a path under the knowledge tree without .md (blueprint/core).
includeDependenciesNoAlso load the assumes: prerequisites of each key. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so safety is covered. The description adds genuinely non-obvious behavior beyond that: each key transitively pulls in its assumes: prerequisites unless includeDependencies is false, and 'all' walks the tree page by page and defers the remainder when the response budget is hit. That deferral/pagination trait is exactly the kind of thing annotations cannot express.

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?

Two sentences, with the usage trigger placed first and the dependency/budget mechanics second. It is dense but every clause carries information; the only slight friction is that 'within the response budget' is compressed enough to need a second read.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only, three-parameter loader with no output schema, the description covers purpose, dependency expansion, and truncation behavior — the things an agent could otherwise get wrong. Remaining gaps are how 'all' interacts with 'keys' and what a returned page record looks like, but these are modest against a fully documented schema and strong annotation coverage.

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%, and every parameter (all, keys, includeDependencies) is already documented in the schema, including the path format and the 'default true' behavior. The description restates that ground rather than adding new semantics, and it does not clarify whether 'all' and 'keys' can be combined or which wins. Baseline 3 is appropriate.

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 opens with a concrete verb and resource: it 'loads Brilliant's Blueprint and design knowledge pages by key' and enumerates the actual keys. That is unambiguous and clearly distinct from the design-mutation siblings (design, edit_design, place_image), so an agent can route to it without opening the schema.

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?

It gives an explicit trigger condition: 'Use this when writing Blueprint rows for a Brilliant design.' That is a real when-to-use signal tied to a workflow, not a vague 'use as needed.' It stops short of a when-not or a named alternative behavior for retrieving knowledge any other way, but the sibling set is a different domain so the gap is minor.

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