Skip to main content
Glama
Sign In
nexterm-mcp

nexterm-mcp

by X1pheR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

nexterm_get_theme

Read-onlyIdempotent

Retrieve theme metadata and content by theme ID to inspect or reuse a Nexterm theme's configuration.

Instructions

Get theme metadata and content.

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": {
      "theme_id": "<theme_id>"
    },
    "name": "nexterm_get_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
theme_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only the notion that both metadata and content are returned, without clarifying format, size, or failure behavior for a nonexistent theme_id.

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?

A single short sentence with no filler, and the key noun phrase is front-loaded. It is efficient, though efficiency here borders on under-specification for a tool with no output schema.

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?

With no output schema, the description should describe what 'content' actually is (raw theme definition, CSS, asset list) and how it differs from nexterm_get_theme_css. It leaves both unanswered, which is insufficient for correct tool selection in a family of four theme-related tools.

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 0%, so the description must carry the burden, but it says nothing about theme_id — not where to obtain it, not whether arbitrary IDs error out. The name is fairly self-explanatory, which keeps this above a 1, but the gap is real.

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 verb+resource pair 'Get theme' is clear, and 'metadata and content' hints at a broader payload than a CSS fetch. However, it does not distinguish this from siblings such as nexterm_get_theme_css or nexterm_list_themes, so an agent cannot tell which to pick from the description alone.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus nexterm_list_themes (to discover IDs) or nexterm_get_theme_css (to fetch styles). No prerequisites, no exclusions, no alternative named.

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