Skip to main content
Glama
Brilliant MCP

Brilliant MCP

Official

create_html

Read-onlyIdempotent

Create HTML content to add or update editable design elements on a collaborative vector canvas, letting agents build and modify designs directly.

Instructions

Retired. A call answers the one line that names the door: edit({ text }) to write, read({ paths }) to read.

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

Input Schema

NameRequiredDescriptionDefault
htmlNo
pathsNo
queryNo
scopeNo
formatNo
blockIdNo
canvasIdNo
elementsNo
sessionIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.10

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and the title 'Retired: use edit or read', so the schema fields carry the safety and deprecation signal. The description adds nothing beyond restating retirement — it does not say what a call actually does now (fails, no-ops, or silently redirects), which is the one behavioral fact an agent needs. No contradiction with annotations, but minimal added value.

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

Conciseness3/5

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

The deprecation notice is correctly front-loaded in a single word, and the whole thing is short with no padding. However, the second sentence is cryptic ('A call answers the one line that names the door') and consumes space without adding actionable meaning, which undercuts the otherwise tight structure.

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

Completeness2/5

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

For a retired tool the essential message is 'do not call this, call these instead', which is present. But with 9 undocumented parameters and no statement about what invoking it returns or raises, an agent that hits this tool via a stray reference has no way to know whether a call is harmless or an error.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are 9 parameters with 0% schema description coverage, and the description explains none of them — html, query, scope, format, blockId, canvasId, elements, and sessionId are entirely undocumented. The only argument shapes mentioned (edit's text, read's paths) belong to sibling tools, not to this one. Even for a retired tool, this leaves nine unexplained fields.

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

Purpose3/5

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

The description opens with 'Retired', which tells the agent the tool is deprecated, but it never states what create_html did or what resource it operated on — that is only inferable from the name. The redirect to edit/read is clear, yet the actual purpose sentence ('A call answers the one line that names the door') is opaque and conveys nothing about the tool itself.

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 explicitly names the replacements and their argument shapes: edit({ text }) to write and read({ paths }) to read, which is direct when-to-use-instead guidance. It stops short of a 5 because it never says whether calling create_html is a no-op or an error, leaving the caller's fallback behavior to inference.

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