Skip to main content
Glama
RMITBLOG

Parallels RAS MCP Server

by RMITBLOG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

RDS Host Pools

ras_infra_get_rds_hostpools
Read-onlyIdempotent

List RDS host pool membership and configuration to review pool composition, check host assignments, or verify load balancing and resource allocation settings.

Instructions

List RDS host pool membership and configuration. Host pools group RDS servers for load balancing and resource allocation. Use this to review pool composition, check host assignments, or verify pool settings.

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

B3.3/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 safety is covered. The description adds only domain background (pools group servers for load balancing) and no behavioral traits beyond the annotations — nothing about response size, pagination, or truncation behavior for a list endpoint.

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?

Three short sentences, front-loaded with the action and resource. The middle sentence is useful background rather than waste, though it is not strictly necessary for invoking the tool.

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 and complete annotations, the description covers what the tool returns conceptually. The absence of an output schema means it could say more about response shape, but nothing essential to calling it 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% and all three parameters (limit, fields, filter) are thoroughly documented in the schema itself, so the baseline is 3. The description contributes no additional parameter meaning — it never mentions filtering or field projection.

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?

The description gives a specific verb ('List') plus resource ('RDS host pool membership and configuration') and explains what host pools are. It is distinguishable from ras_infra_get_rds_hosts and ras_infra_get_vdi_hostpools by the RDS-hostpool framing, though it never explicitly contrasts them.

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?

It offers three concrete use cases ('review pool composition, check host assignments, or verify pool settings'), which implies when to reach for it. However, it never names the adjacent tools (ras_infra_get_rds_hosts, ras_infra_get_vdi_hostpools) or states any exclusion, so the agent must infer the boundary itself.

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