Skip to main content
Glama
Sign In

PixelGlass

by co.pixelglass
OverviewDiscussionsAdmin

Get a theme's settings

get_theme_settings
Read-onlyDestructive

On one site of the account, named in site. The settings the theme's manifest declares under config.custom (the theme contract, "Theme settings") — each with its type, options, group, label, default and the value the site has set, as the template reads it through theme.<key>. Rows, not files: reading them installs nothing and touches no file. A text setting holding prose a reader reads — an intro, a tagline, a heading — should be declared html in the manifest, so the publisher gets the rich-text editor; change the declaration with edit_theme_file.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>",
      "theme": "<theme>"
    },
    "name": "get_theme_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesThe site to work on, as list_sites names it
themeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already carry readOnlyHint=true and openWorldHint=true, but the description adds real behavioral evidence: reading rows "installs nothing and touches no file," and the result contains both declared metadata and the site's current value as read through `theme.<key>`. Note that destructiveHint=true is internally inconsistent with readOnlyHint=true, but it is redundant per the MCP spec, so the description's read-only claim is not a genuine contradiction.

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 core content is dense and useful, but the description opens with a grammatical fragment, and the closing tip about declaring text settings as html with edit_theme_file is tangential to invoking this read tool. It buries the primary read semantics in a long first sentence.

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?

There is no output schema, so the description usefully enumerates the returned fields, but it omits the format of the `theme` argument and any error behavior (missing theme, no custom settings). For a two-parameter read tool this is adequate but leaves real gaps.

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?

Schema description coverage is only 50%: `site` is documented in the schema, while `theme` has no description at all. The description restates site scoping ("On one site of the account, named in site") — value already in the schema — and never explains how a theme is identified (name, handle, id) or what happens for a theme without config.custom.

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

Purpose4/5

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

The description names the specific resource: the theme's manifest settings under config.custom, each with type, options, group, label, default and the site's configured value. It also distinguishes the shape of the result ("Rows, not files"), which separates it from read_theme_file and list_theme_files. The only weakness is the fragmentary opening ("On one site of the account, named in site.") that delays a clean statement of the verb.

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?

Usage is implied rather than stated: reading settings installs nothing, and declaration changes go to edit_theme_file. However, it never names set_theme_settings as the mutation counterpart, and never says when NOT to use this tool (e.g., for theme file contents or the theme's build status).

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

All PixelGlass toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources