Lovie Company Formation

Get Wired Transactions

cap_table_get_wired_transactions

Read-only

GetWiredTransactions returns the confirmed-wire ledger (wired + refunded investor rows) for the fundraising Transactions page. Read-only.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`totalCount`	No
`transactions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedSep 10, 2026
- addedOutput schema / properties / transactions / items / properties / roundId / anyOf
```
Added value: +[
+  {
+    "description": "UUID value wrapper.",
+    "properties": {
+      "value": {
+        "format": "uuid",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / transactions / items / properties / roundId / description
```
Removed value: -"UUID value wrapper."
```
- removedOutput schema / properties / transactions / items / properties / roundId / properties
```
Removed value: -{
-  "value": {
-    "format": "uuid",
-    "type": "string"
-  }
-}
```
- removedOutput schema / properties / transactions / items / properties / roundId / type
```
Removed value: -"object"
```
- addedOutput schema / properties / transactions / items / properties / stakeholderId / anyOf
```
Added value: +[
+  {
+    "description": "UUID value wrapper.",
+    "properties": {
+      "value": {
+        "format": "uuid",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / transactions / items / properties / stakeholderId / description
```
Removed value: -"UUID value wrapper."
```
- removedOutput schema / properties / transactions / items / properties / stakeholderId / properties
```
Removed value: -{
-  "value": {
-    "format": "uuid",
-    "type": "string"
-  }
-}
```
- removedOutput schema / properties / transactions / items / properties / stakeholderId / type
```
Removed value: -"object"
```
- addedOutput schema / properties / transactions / items / properties / wiredAt / anyOf
```
Added value: +[
+  {
+    "format": "date-time",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / transactions / items / properties / wiredAt / format
```
Removed value: -"date-time"
```
- removedOutput schema / properties / transactions / items / properties / wiredAt / type
```
Removed value: -"string"
```
First observedAug 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the read-only and non-destructive profile, so the description's contribution is the extra detail that the ledger includes both wired and refunded investor rows. This is non-obvious and useful. It does not discuss pagination or ordering, but the output schema exists and the annotations lower the burden.

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?

The description is a single front-loaded sentence followed by 'Read-only.' Every word earns its place, and there is no redundancy or filler.

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?

For a one-parameter read-only tool with annotations and an output schema, the description provides all necessary context: what data is returned, in what scope, and for which page. No critical missing information prevents an agent from selecting or invoking it correctly.

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?

With 100% schema description coverage and only one self-explanatory companyId parameter, the description does not need to add parameter detail. The description does not deepen parameter semantics, but the schema already covers the UUID wrapper, so baseline 3 is appropriate.

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?

The description names a specific verb ('returns'), a clear resource ('confirmed-wire ledger'), and defines the scope precisely ('wired + refunded investor rows'). This distinguishes it from other cap_table_get_* tools, especially transaction-related siblings like cap_table_get_transaction_summary or cap_table_get_list_cap_table_wire_match_suggestions.

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?

The phrase 'for the fundraising Transactions page' gives clear context about when this tool is relevant. However, it does not explicitly name alternatives or exclusion conditions, so it stops short of full when/when-not guidance.

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.