Skip to main content
Glama
Sign In

InsideOut (Riley)

by com.luthersystems.app
OverviewDiscussionsAdmin

Await Cloud Credentials

credawait
Idempotent

Wait for the user to securely connect their cloud account and subscribe to Luther Systems. Polls until credentials appear on the session.

šŸŽÆ USE THIS TOOL WHEN: tfdeploy returns an 'auth_required', 'no_credentials', or 'credentials_expired' error.

The user needs to visit the connect URL to:

  1. Connect their cloud credentials (AWS or GCP)

  2. Sign up and subscribe to a Luther Systems plan (required for deployment)

This secure connection allows InsideOut to deploy and manage infrastructure in the user's cloud account on their behalf. Credentials are handled securely and only used for deployment and management sessions.

WORKFLOW:

  1. FIRST: Present the connect URL and explanation to the user (from the tfdeploy error response)

  2. THEN: Call this tool to begin polling for credentials

  3. The user opens the URL in their browser to subscribe and add credentials

  4. When credentials are found, inform the user and call tfdeploy to deploy

IMPORTANT: Do NOT call this tool without first showing the connect URL to the user. The user needs to see the URL to complete the process.

REQUIRES: session_id from convoopen response (format: sess_v2_...). OPTIONAL: cloud ('aws' or 'gcp'), timeout (integer, seconds to wait, default 300, max 600).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "session_id": "<session_id>"
    },
    "name": "credawait"
  }
}

Input Schema

NameRequiredDescriptionDefault
cloudNoCloud provider whose credentials are awaited: 'aws' or 'gcp'. Defaults to 'aws'.
timeoutNoMax seconds to wait for the user to complete the browser-based credential connect flow. Default 300, max 600.
session_idYesSession ID from convoopen ā€” pass back EXACTLY as returned, including the ?token=... suffix (format: sess_v2_*?token=*). The suffix is part of the session credential; never strip it when summarizing.

Output Schema

NameRequiredDescriptionDefault
cloudNoCloud provider: 'aws' or 'gcp'.
hintsNoGuidance for the calling agent: what to do next and which tools relate to this result.
statusNo'connected' when credentials were found, or 'timeout' when the wait ended first (call credawait again).
session_idNoSession ID this result belongs to (format sess_v2_*?token=*). Pass it back verbatim to later tools.
auth_methodNoHow the credentials were connected, when status is 'connected'.
connect_urlNoURL the user opens to connect credentials, when status is 'timeout'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "auth_method": {
+      "description": "How the credentials were connected, when status is 'connected'.",
+      "type": "string"
+    },
+    "cloud": {
+      "description": "Cloud provider: 'aws' or 'gcp'.",
+      "type": "string"
+    },
+    "connect_url": {
+      "description": "URL the user opens to connect credentials, when status is 'timeout'.",
+      "type": "string"
+    },
+    "hints": {
+      "description": "Guidance for the calling agent: what to do next and which tools relate to this result.",
+      "properties": {
+        "next_actions": {
+          "description": "Suggested next steps, in order, often as ready-to-run tool calls.",
+          "items": {
+            "description": "One suggested next step.",
+            "type": "string"
+          },
+          "type": [
+            "null",
+            "array"
+          ]
+        },
+        "related_tools": {
+          "description": "Names of tools that are useful after this result.",
+          "items": {
+            "description": "A tool name.",
+            "type": "string"
+          },
+          "type": [
+            "null",
+            "array"
+          ]
+        }
+      },
+      "type": [
+        "null",
+        "object"
+      ]
+    },
+    "session_id": {
+      "description": "Session ID this result belongs to (format sess_v2_*?token=*). Pass it back verbatim to later tools.",
+      "type": "string"
+    },
+    "status": {
+      "description": "'connected' when credentials were found, or 'timeout' when the wait ended first (call credawait again).",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed7 schema fields changed
    • addedInput schema / properties / cloud / description
      Added value: +"Cloud provider whose credentials are awaited: 'aws' or 'gcp'. Defaults to 'aws'."
    • addedInput schema / properties / cloud / enum
      Added value: +[
+  "aws",
+  "gcp"
+]
    • addedInput schema / properties / session_id / description
      Added value: +"Session ID from convoopen ā€” pass back EXACTLY as returned, including the ?token=... suffix (format: sess_v2_*?token=*). The suffix is part of the session credential; never strip it when summarizing."
    • addedInput schema / properties / session_id / pattern
      Added value: +"^sess_v2_[0-9A-Za-z]+\\?token=[0-9a-f]+$"
    • addedInput schema / properties / timeout / description
      Added value: +"Max seconds to wait for the user to complete the browser-based credential connect flow. Default 300, max 600."
    • addedInput schema / properties / timeout / maximum
      Added value: +600
    • addedInput schema / properties / timeout / minimum
      Added value: +1
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover the safety profile (non-destructive, idempotent, open-world); the description adds the blocking/polling behavior, the timeout bound, the prerequisite that a URL must be surfaced first, and how credentials are used. That is substantial context beyond what structured fields provide.

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?

Well front-loaded with headers and a numbered workflow that an agent can act on. Slightly over-written: the 'IMPORTANT: do not call without showing URL' maxim restates workflow step 1, and the InsideOut security paragraph is persuasive filler rather than operational guidance.

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?

Given an output schema exists, return values needn't be explained; prerequisites, session source, trigger errors, timeout semantics, and the post-success next step (call tfdeploy) are all present. Nothing an agent needs to invoke 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 coverage is 100% and the description largely restates it (session_id from convoopen, cloud aws/gcp, timeout default 300 max 600). The one added nuance, that the ?token= suffix is part of the session credential and must not be stripped, is also already in the schema, so this is baseline rather than enrichment.

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: wait/poll for the user's cloud credentials to appear on the session. The Luther Systems subscription step and the polling mechanism make it clearly distinct from siblings like convoawait or tfstatus.

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

Usage Guidelines5/5

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

Explicit trigger condition ('tfdeploy returns auth_required, no_credentials, or credentials_expired'), explicit ordering rule ('Do NOT call without first showing the connect URL'), and a numbered workflow that names tfdeploy as the follow-up. Both when-to-use and when-not-to-use are covered.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All InsideOut (Riley) toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources