Skip to main content
Glama
Sign In

InsideOut (Riley)

by com.luthersystems.app
OverviewDiscussionsAdmin

Await Pending Response

convoawait
Read-only

Wait for a pending response from Riley after a convoreply timeout.

šŸŽÆ USE THIS TOOL WHEN: convoreply returned a timeout error. This allows you to continue waiting for the response without resending the message.

REQUIRES:

  • session_id: from convoopen response

OPTIONAL:

  • message_id: if known (from convoreply timeout error)

  • timeout (integer): seconds to wait. For Cursor, use 50 (default). Max 55.

Returns the same format as convoreply when successful.

Input Schema

NameRequiredDescriptionDefault
timeoutNoMax seconds to wait. Default 50, max 55.
message_idNoOptional message ID from a convoreply timeout error. Not required for normal turn-based flow.
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
hintsNoGuidance for the calling agent: what to do next and which tools relate to this result.
sourceNoHow the reply was found when it did not come from the pending convoreply call: 'poll' or 'targeted_poll'.
statusNoOutcome of the call: 'ok' (Riley replied), 'timeout' (still working; call convoawait), or 'pending_exists' (an earlier reply is still pending; call convoawait).
message_idNoID of Riley's reply message.
session_idNoSession ID this result belongs to (format sess_v2_*?token=*). Pass it back verbatim to later tools.
instructionNoPlain-language instruction for the agent when the reply is not ready yet.
next_actionNoTool to call next when the reply is not ready yet (for example 'convoawait').
terraform_readyNoTrue when Riley signalled that the design is final and tfgenerate can be called.
assistant_messageNoRiley's reply, cleaned of internal markers. Show it to the user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "assistant_message": {
+      "description": "Riley's reply, cleaned of internal markers. Show it to the user.",
+      "properties": {
+        "text": {
+          "description": "The message text.",
+          "type": "string"
+        }
+      },
+      "type": [
+        "null",
+        "object"
+      ]
+    },
+    "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"
+      ]
+    },
+    "instruction": {
+      "description": "Plain-language instruction for the agent when the reply is not ready yet.",
+      "type": "string"
+    },
+    "message_id": {
+      "description": "ID of Riley's reply message.",
+      "type": "string"
+    },
+    "next_action": {
+      "description": "Tool to call next when the reply is not ready yet (for example 'convoawait').",
+      "type": "string"
+    },
+    "session_id": {
+      "description": "Session ID this result belongs to (format sess_v2_*?token=*). Pass it back verbatim to later tools.",
+      "type": "string"
+    },
+    "source": {
+      "description": "How the reply was found when it did not come from the pending convoreply call: 'poll' or 'targeted_poll'.",
+      "type": "string"
+    },
+    "status": {
+      "description": "Outcome of the call: 'ok' (Riley replied), 'timeout' (still working; call convoawait), or 'pending_exists' (an earlier reply is still pending; call convoawait).",
+      "type": "string"
+    },
+    "terraform_ready": {
+      "description": "True when Riley signalled that the design is final and tfgenerate can be called.",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. Changed6 schema fields changed
    • addedInput schema / properties / message_id / description
      Added value: +"Optional message ID from a convoreply timeout error. Not required for normal turn-based flow."
    • 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. Default 50, max 55."
    • addedInput schema / properties / timeout / maximum
      Added value: +55
    • addedInput schema / properties / timeout / minimum
      Added value: +1
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=true, idempotentHint=false), so the bar is lower. The description adds real behavioral context: this is a blocking wait operation, it requires the session_id credential from convoopen, and it enforces a max timeout of 55s (default 50, Cursor-specific). It doesn't discuss failure modes if the wait times out again, but overall it meaningfully supplements the annotations.

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?

Front-loaded with the core purpose, then clearly sectioned into USE WHEN / REQUIRES / OPTIONAL. Headers and emoji are slightly decorative but every line carries actionable information with no redundant filler.

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?

Covers the trigger condition, credential source, and timeout constraints for a blocking tool. An output schema exists, so the brief 'returns the same format as convoreply' note is sufficient and the description needn't detail return values further.

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 the schema already documents all three parameters including the token-suffix requirement on session_id. The description restates the required/optional split and the source of session_id (convoopen), adding only marginal value beyond what the schema provides, which matches the baseline 3.

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+resource: waiting for a pending response from Riley after a convoreply timeout. It explicitly distinguishes itself from the sibling convoreply by noting it continues waiting 'without resending the message', so an agent can tell them apart without opening either schema.

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 'USE THIS TOOL WHEN: convoreply returned a timeout error' gives the exact triggering condition and names the alternative tool (convoreply). When-to-use is unambiguous and no inference is required.

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
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources