Lovie Company Formation

Get Issuance State

banking_get_issuance_state

Read-only

GetIssuanceState reports where this application's deposit account stands: whether it is queued, being opened, open, or could not be opened, and the last four digits once there are any. It exists as its own state so that an approved application is never mistaken for an open account. Approval is our banking partner accepting the corporation; opening happens after it and can still fail, so a caller that wants to tell somebody they can receive money must read this, not the application's status.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`applicationId`	Yes	UUID value wrapper.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`issuance`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 29, 2026

changedOutput schema / properties / issuance / anyOf

Previous value: -[
-  {
-    "properties": {
-      "accountId": {
-        "anyOf": [
-          {
-            "description": "UUID value wrapper.",
-            "properties": {
-              "value": {
-                "format": "uuid",
-                "type": "string"
-              }
-            },
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "accountNumberLast4": {
-        "type": "string"
-      },
-      "issuedAt": {
-        "anyOf": [
-          {
-            "format": "date-time",
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "lastError": {
-        "anyOf": [
-          {
-            "description": "Free-form description (max 5000 chars).",
-            "properties": {
-              "value": {
-                "maxLength": 5000,
-                "type": "string"
-              }
-            },
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "provider": {
-        "anyOf": [
-          {
-            "description": "Lowercase kebab-case code identifier.",
-            "properties": {
-              "value": {
-                "pattern": "^[a-z0-9]+(-[a-z0-9]+)*$",
-                "type": "string"
-              }
-            },
-            "type": "object"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "routingNumberLast4": {
-        "type": "string"
-      },
-      "status": {
-        "enum": [
-          "ISSUANCE_STATUS_UNSPECIFIED",
-          "ISSUANCE_STATUS_BLOCKED",
-          "ISSUANCE_STATUS_QUEUED",
-          "ISSUANCE_STATUS_IN_FLIGHT",
-          "ISSUANCE_STATUS_ISSUED",
-          "ISSUANCE_STATUS_FAILED",
-          "ISSUANCE_STATUS_CANCELLED"
-        ],
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "accountId": {
+        "anyOf": [
+          {
+            "description": "UUID value wrapper.",
+            "properties": {
+              "value": {
+                "format": "uuid",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "accountNumberLast4": {
+        "type": "string"
+      },
+      "issuedAt": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "lastError": {
+        "anyOf": [
+          {
+            "description": "Free-form description (max 5000 chars).",
+            "properties": {
+              "value": {
+                "maxLength": 5000,
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "provider": {
+        "anyOf": [
+          {
+            "description": "Lowercase kebab-case code identifier.",
+            "properties": {
+              "value": {
+                "pattern": "^[a-z0-9]+(-[a-z0-9]+)*$",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "routingNumberLast4": {
+        "type": "string"
+      },
+      "status": {
+        "enum": [
+          "ISSUANCE_STATUS_UNSPECIFIED",
+          "ISSUANCE_STATUS_BLOCKED",
+          "ISSUANCE_STATUS_QUEUED",
+          "ISSUANCE_STATUS_IN_FLIGHT",
+          "ISSUANCE_STATUS_ISSUED",
+          "ISSUANCE_STATUS_FAILED",
+          "ISSUANCE_STATUS_CANCELLED",
+          "ISSUANCE_STATUS_HELD_IDENTITY"
+        ],
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

AddedSep 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful non-annotation semantics: approval is the partner accepting the corporation, opening happens afterward and can still fail, and an approved application must not be mistaken for an open account. It stops short of mentioning auth or freshness/polling behavior, so 4 rather than 5.

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 sentences, all front-loaded with the core purpose first, then the state-enumeration rationale. Every sentence earns its place, though the approval-vs-open explanation is slightly repetitive with the earlier statement.

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?

An output schema exists, so return values need not be explained, and the description still names the state values and the last-four-digits detail. It complements the read-only annotations adequately; only auth/freshness expectations are absent, which is a minor gap.

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% for the single applicationId parameter, so the schema already documents it. The description adds nothing about the parameter (e.g., which application ID, relationship to the banking application flow). Baseline 3 applies when the schema does the heavy lifting.

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 ('reports where this application's deposit account stands') and enumerates the states it returns (queued, opening, open, failed) plus last four digits. It explicitly differentiates itself from the banking application's status, so an agent can pick it apart from banking_get_banking_application 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?

Gives an explicit when-to-use: a caller who wants to tell somebody they can receive money must read this, not the application's status. It names the alternative concept (application status) and the condition that selects this tool over it.

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

All Lovie Company Formation tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.