Skip to main content
Glama
RMITBLOG

Parallels RAS MCP Server

by RMITBLOG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

SAML Identity Providers

ras_infra_get_saml_idps
Read-onlyIdempotent

List SAML identity providers configured for SSO to audit setup or troubleshoot authentication. Retrieve provider names, metadata URLs, and configuration details.

Instructions

List SAML identity providers configured for SSO — provider names, metadata URLs, configuration details. Use this to audit SSO configuration or troubleshoot SAML authentication.

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/5.0
Behavior4/5

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

Annotations already declare the safe read-only/idempotent/non-destructive profile, so the bar is lower. The description adds useful value by naming the returned content (provider names, metadata URLs, configuration details), which annotations cannot convey; pagination/edge behavior is left to the schema.

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?

Two compact sentences, front-loaded with the resource and a dash-list of returned fields, followed immediately by the use case. No filler or redundancy.

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?

Given no output schema, the description usefully sketches the return shape, and annotations plus a 100%-covered schema carry the rest. Adequately complete, with only minor omissions around result volume or filtering behavior.

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%, so limit, fields, and filter are fully documented in the schema itself. The description adds no syntax or semantics beyond that, making the baseline 3 appropriate.

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?

Specific verb (List) plus a precise resource (SAML identity providers) scoped to SSO, with the returned fields enumerated. An agent can tell what it retrieves, though it does not explicitly differentiate itself from near-neighbors like ras_infra_get_providers or ras_site_get_mfa.

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?

Explicitly frames the use case — auditing SSO configuration and troubleshooting SAML authentication — which gives clear context for when to call it. It stops short of naming a sibling alternative or stating when not to use it.

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