Skip to main content
Glama
Brilliant MCP

Brilliant MCP

Official

create_modify_elements

Read-onlyIdempotent

Routes element creation and modification calls to the right tool: use edit({ text }) to write or read({ paths }) to read canvas content.

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_modify_elements"
  }
}

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

A3.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and destructiveHint=false, which is consistent with a retired no-op, and the description adds the crucial context that the tool is retired and should be bypassed. What it omits is what actually happens on invocation — an error, an empty result, or a silent no-op — which would matter to an agent that calls it anyway.

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, front-loaded with the decisive word 'Retired,' and nothing extraneous. The metaphor 'the one line that names the door' is slightly cryptic and costs a moment of parsing where plain phrasing would not.

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?

For a retired tool the essential message — do not call this, use edit or read — is fully delivered, and no output schema exists to explain. However, with nine undocumented parameters and no statement of what a call returns or raises, an agent lacks the full picture of the retirement behavior.

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?

Nine parameters with 0% schema description coverage are left completely unexplained; the only parameter-like token mentioned, paths, is presented as an argument to the sibling read() rather than as documentation for this schema. Since the tool is retired this is largely moot, but by the stated standard the description does not compensate for the coverage gap.

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 leads with 'Retired,' which tells an agent the tool's operational status but never states what create_modify_elements originally did or what its nine parameters address. It does name the replacements (edit, read), so an agent can route away, but the purpose of the tool itself is left entirely implicit.

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 explicitly maps intent to alternative: edit({ text }) for writes and read({ paths }) for reads, naming both sibling tools and the argument each expects. There is no ambiguity about when to use this tool versus its replacements — the answer is never, use those instead.

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