Super Artifacts

How the tools fit together

super_help

Read-only

Plain-text notes for when it is unclear which tool, data store or argument shape does a job. Topics: tools (a line per tool), data (which store a page needs and how the page writes to it), templates (finding, building from, drafting, releasing), collections (content models and field types), projects (creating, ordering, sharing, rules), batch (what each tool takes in one call). Without topic: the full topic list, which names two more reached from results. Answers {topic, text}; not needed when a tool’s own description answers the question.

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

Input Schema

Name	Required	Description	Default
`topic`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds useful behavioral detail: omitting `topic` returns the full topic list, the list names two more reachable from results, and the return shape is `{topic, text}`.

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?

The description is dense but front-loaded with the purpose, then the topic list, then default behavior and return shape. The topic list is long but necessary; the phrase 'which names two more reached from results' is slightly opaque but does not waste substantial space.

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?

For a read-only help tool with one optional enum parameter and no output schema, the description covers use conditions, all topic values, default behavior without `topic`, and the response shape `{topic, text}`. Nothing essential for correct invocation appears missing.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the parameter meaning. It does so by explaining every enum value's subject matter (`tools`, `data`, `templates`, `collections`, `projects`, `batch`) and describing what happens when `topic` is omitted.

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?

States that this is a plain-text notes/help tool for when it is unclear which tool, data store, or argument shape to use, and enumerates the specific topics it covers. It also distinguishes itself from normal tool descriptions by saying it is not needed when a tool's own description already answers the question.

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?

Explicitly gives the condition for use ('when it is unclear which tool, data store or argument shape does a job') and the condition against use ('not needed when a tool’s own description answers the question'). The topic list further routes the agent to the appropriate help area.

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

All Super Artifacts tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?