Skip to main content
Glama
Sign In
nexterm-mcp

nexterm-mcp

by X1pheR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

nexterm_get_theme_css

Read-onlyIdempotent

Retrieves the CSS stylesheet for a specified Nexterm theme by theme ID, enabling you to inspect or apply that theme's styling.

Instructions

Get CSS for one theme.

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

Input Schema

NameRequiredDescriptionDefault
theme_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond that — not what the returned CSS covers (variables, classes), nor format or size. openWorldHint=true is also unexplained.

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?

One front-loaded sentence with zero waste, but it is under-specified rather than merely tight — 'conciseness' here comes at the cost of missing essential context.

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?

No output schema exists, so the description should explain what the CSS return value is (a stylesheet string? scoped to variables?) and how theme_id is obtained. Neither is present, leaving an agent guessing about the payload it will get back.

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% and the single parameter theme_id has only type/minimum in the schema. The description says 'one theme' but never explains that theme_id is a numeric theme identifier obtained from nexterm_list_themes, so it fails to 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?

States a verb (Get) and resource (CSS for one theme), so the basic action is clear. But it doesn't distinguish itself from the closely related sibling nexterm_get_active_theme_css (and nexterm_get_theme), leaving the 'one theme' vs 'active theme' distinction implicit.

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?

No indication of when to call this versus nexterm_get_active_theme_css or nexterm_get_theme, and no note that theme_id must come from nexterm_list_themes. The agent must infer the usage from sibling names alone.

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