Skip to main content
Glama
RMITBLOG

Parallels RAS MCP Server

by RMITBLOG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Themes

ras_infra_get_themes
Read-onlyIdempotent

List user portal themes configured in a RAS farm to review branding, logos, and customization settings. Use it to verify theme assignments and portal appearance configuration.

Instructions

List user portal themes configured in the RAS farm — branding, logos, customisation settings. Use this to review portal appearance configuration or verify theme assignments.

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows after filtering. Default 50, max 200. Prefer narrowing with `filter` over raising the limit.
fieldsNoTop-level keys to keep on each row. Unknown keys are dropped. Use this to shrink large responses to only the columns you need.
filterNoEquality filter on top-level fields (AND across keys). String values match case-insensitively.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.3.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / fields
      Added value: +{
+  "description": "Top-level keys to keep on each row. Unknown keys are dropped. Use this to shrink large responses to only the columns you need.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
    • addedInput schema / properties / filter
      Added value: +{
+  "additionalProperties": {
+    "type": [
+      "string",
+      "number",
+      "boolean"
+    ]
+  },
+  "description": "Equality filter on top-level fields (AND across keys). String values match case-insensitively.",
+  "type": "object"
+}
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max rows after filtering. Default 50, max 200. Prefer narrowing with `filter` over raising the limit.",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}
  2. First observedv1.0.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, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered structurally. The description adds only the content inventory (branding, logos, settings) and says nothing about pagination, response size, or auth requirements.

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?

Two short sentences, verb-first and front-loaded, with no obvious padding. The second sentence is mildly redundant with the first but still adds a usable framing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only list tool with a fully documented schema, complete annotation coverage, and no output schema, the description tells the agent what the resource contains and when to reach for it. Return shape and pagination remain unspecified, but the schema's limit/filter/fields params largely cover that.

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?

Schema description coverage is 100% and all three parameters (limit, fields, filter) are well documented in the schema itself. The description adds no parameter guidance, so the baseline 3 applies.

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 ('List user portal themes configured in the RAS farm') and enumerates the content returned (branding, logos, customisation settings). It is clearly distinct from siblings like ras_infra_get_agents or ras_infra_get_sites, though it never names a sibling to contrast against.

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?

'Use this to review portal appearance configuration or verify theme assignments' gives a use case, but it largely restates the purpose rather than distinguishing it from alternatives or giving conditions/exclusions. With no closely related sibling, the implied-usage bar is met but nothing more.

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