Skip to main content
Glama
RMITBLOG

Parallels RAS MCP Server

by RMITBLOG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

All Published Items

ras_pub_get_all_items
Read-onlyIdempotent

List all published RDS, VDI, and AVD apps and desktops in one view. Filter or project fields to narrow large farm results.

Instructions

List all published items across all resource types (RDS, VDI, AVD apps and desktops) in a single view. Use this for a complete overview of everything published in the farm. Large farms can return thousands of items — narrow with filter (e.g. {type: 'App'}) or project with fields to keep responses small.

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

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context beyond the annotations: large farms can return thousands of items and responses can be kept small via filter/fields, which is a scale/performance disclosure the annotations do not carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with what the tool returns, then the usage condition, then the scale mitigation. No redundancy and every sentence carries information an agent needs.

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

Completeness5/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 still conveys the return shape (items across all published resource types in a single view), the volume risk, and the two levers for controlling it. Combined with the fully documented schema, nothing an agent needs to call this correctly is missing.

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%, with limit, fields and filter each documented in the schema itself (including the default of 50, max 200, and the preference for narrowing over raising limit). The description's filter example {type: 'App'} hints at usable top-level keys, but this is marginal added value over the schema, so baseline 3 applies.

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

Purpose5/5

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

States a specific verb and resource (list all published items) and explicitly scopes it across all resource types (RDS, VDI, AVD apps and desktops), which distinguishes it from the per-type siblings like ras_pub_get_rds_apps and ras_pub_get_vdi_desktops. An agent can identify this as the aggregate cross-type listing without opening any schema.

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

Usage Guidelines4/5

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

"Use this for a complete overview of everything published in the farm" gives a clear selection context, implicitly positioning it against the per-type getters. It also advises narrowing with filter or project with fields for large farms. It stops short of naming the sibling alternatives explicitly or stating when not to use this tool.

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