Skip to main content
Glama
Sign In
appsmith-mcp

appsmith-mcp

by t0knight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

list_themes

List available themes for the current application, including built-in and custom themes with details such as id, name, displayName, and system theme status.

Instructions

List the themes available to the current application — built-in plus any saved custom themes. Each entry has id, name, displayName, and isSystemTheme.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations provided, so the description carries the burden of disclosing behavior. It correctly implies a non-destructive read operation and clarifies the scope (current app, built-in + custom). However, it does not explicitly state invariants like 'no side effects' or permissions.

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

Conciseness5/5

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

Two concise sentences, front-loaded with the primary purpose and then the output fields. No redundant or unnecessary information.

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?

The description fully explains what the tool returns (list of themes with id, name, displayName, isSystemTheme) and its scope (current app, built-in + custom). Given no output schema, this is complete and sufficient for an agent to understand the tool's functionality.

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?

There are no parameters, and the input schema is fully covered (trivially 100%). The description adds no parameter information but does explain the output structure, which is useful but beyond this dimension.

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 clearly states the tool lists themes available to the current application, specifying both built-in and custom themes, and distinguishes from siblings like get_current_theme (single theme) and set_theme (applying a theme). The verb 'list' and resource 'themes' are specific.

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

Usage Guidelines3/5

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

No explicit guidance on when to use versus alternatives; however, the description implies it is for obtaining the full list, and the sibling names (get_current_theme, set_theme, etc.) provide context. Usage is implied but not explicitly stated.

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

Deploy Server

Other Tools