Skip to main content
Glama
Sign In
nexterm-mcp

nexterm-mcp

by X1pheR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

nexterm_get_active_theme_css

Read-onlyIdempotent

Retrieve the CSS for the configured account's active theme. Use it to fetch current styling rules from the Nexterm server for UI theming or customization.

Instructions

Get CSS for the configured account's active theme.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the resource is scoped to the configured account's active theme (i.e., no id argument needed), but says nothing about the returned form of the CSS or whether it reflects unsaved/updated themes.

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 scope qualifier is placed before the resource. It is efficient, though slightly terse for the only prose the agent gets.

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?

With no output schema and no parameters, the description is the only place to learn what comes back (a CSS string? an object?) and whether it errors when no theme is active. That is left unaddressed, though the core call semantics are clear.

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

Parameters4/5

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

The tool takes zero parameters and the schema is an EmptyInput object, so there is nothing for the description to disambiguate. Baseline 4 applies; the description correctly implies no identifier is required.

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?

States a specific verb and resource ('Get CSS') and scopes it to 'the configured account's active theme', which implicitly separates it from nexterm_get_theme_css (which takes a theme identifier). It does not explicitly name that sibling, so the differentiation is inferred rather than stated.

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 only implied: fetch the CSS of whatever theme is currently active. There is no explicit 'use X when you want CSS for a specific theme id' routing to nexterm_get_theme_css or nexterm_set_active_theme, which an agent would likely need to disambiguate.

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