Lovie Company Formation

Get Payment

payment_get_payment

Read-only

Returns one payment received against an invoice, by id: amount, date, method and the invoice it was applied to. Read-only.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`payment`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 10, 2026

addedOutput schema / properties / payment / anyOf

Added value: +[
+  {
+    "properties": {
+      "amountCents": {
+        "type": "string"
+      },
+      "companyId": {
+        "anyOf": [
+          {
+            "description": "UUID value wrapper.",
+            "properties": {
+              "value": {
+                "format": "uuid",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "createdAt": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "currency": {
+        "type": "string"
+      },
+      "description": {
+        "type": "string"
+      },
+      "destinationAccountId": {
+        "anyOf": [
+          {
+            "description": "UUID value wrapper.",
+            "properties": {
+              "value": {
+                "format": "uuid",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "id": {
+        "anyOf": [
+          {
+            "description": "UUID value wrapper.",
+            "properties": {
+              "value": {
+                "format": "uuid",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "initiatedAt": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "providerReference": {
+        "type": "string"
+      },
+      "settledAt": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "sourceAccountId": {
+        "anyOf": [
+          {
+            "description": "UUID value wrapper.",
+            "properties": {
+              "value": {
+                "format": "uuid",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "status": {
+        "enum": [
+          "PAYMENT_STATUS_UNSPECIFIED",
+          "PAYMENT_STATUS_PENDING",
+          "PAYMENT_STATUS_SETTLED",
+          "PAYMENT_STATUS_FAILED",
+          "PAYMENT_STATUS_CANCELLED"
+        ],
+        "type": "string"
+      },
+      "type": {
+        "enum": [
+          "PAYMENT_TYPE_UNSPECIFIED",
+          "PAYMENT_TYPE_TRANSFER",
+          "PAYMENT_TYPE_DEPOSIT",
+          "PAYMENT_TYPE_WITHDRAWAL"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "companyId"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / payment / properties

Removed value: -{
-  "amountCents": {
-    "type": "string"
-  },
-  "companyId": {
-    "description": "UUID value wrapper.",
-    "properties": {
-      "value": {
-        "format": "uuid",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "createdAt": {
-    "format": "date-time",
-    "type": "string"
-  },
-  "currency": {
-    "type": "string"
-  },
-  "description": {
-    "type": "string"
-  },
-  "destinationAccountId": {
-    "description": "UUID value wrapper.",
-    "properties": {
-      "value": {
-        "format": "uuid",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "id": {
-    "description": "UUID value wrapper.",
-    "properties": {
-      "value": {
-        "format": "uuid",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "initiatedAt": {
-    "format": "date-time",
-    "type": "string"
-  },
-  "providerReference": {
-    "type": "string"
-  },
-  "settledAt": {
-    "format": "date-time",
-    "type": "string"
-  },
-  "sourceAccountId": {
-    "description": "UUID value wrapper.",
-    "properties": {
-      "value": {
-        "format": "uuid",
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "status": {
-    "enum": [
-      "PAYMENT_STATUS_UNSPECIFIED",
-      "PAYMENT_STATUS_PENDING",
-      "PAYMENT_STATUS_SETTLED",
-      "PAYMENT_STATUS_FAILED",
-      "PAYMENT_STATUS_CANCELLED"
-    ],
-    "type": "string"
-  },
-  "type": {
-    "enum": [
-      "PAYMENT_TYPE_UNSPECIFIED",
-      "PAYMENT_TYPE_TRANSFER",
-      "PAYMENT_TYPE_DEPOSIT",
-      "PAYMENT_TYPE_WITHDRAWAL"
-    ],
-    "type": "string"
-  }
-}

removedOutput schema / properties / payment / required
```
Removed value: -[
-  "companyId"
-]
```
removedOutput schema / properties / payment / type
```
Removed value: -"object"
```

First observedAug 11, 2026

TDQS

A3.9/5.0

Behavior3/5

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so 'Read-only' in the description adds no new behavioral disclosure. It does add useful context that payments are received against invoices, but it doesn't mention behavior on missing ids, errors, or permissions.

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 one tight sentence that front-loads the resource and lookup method, then lists the key returned fields. 'Read-only' adds a single useful word with no waste.

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 simple getter with fully covered schema and an output schema present, the description covers what is returned, how it is selected, and the key fields. Nothing needed to invoke this tool correctly appears 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?

The schema already provides 100% description coverage, including the UUID value wrapper and format. The description's 'by id' confirms the parameter's role but adds no format or semantic detail beyond what the schema already provides.

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 specific resource ('one payment ... by id'), and enumerates the returned fields (amount, date, method, invoice). This clearly distinguishes it from the list-oriented sibling payment_get_list_payments.

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

Usage Guidelines3/5

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

The tool's use case is implied: retrieve a single payment by id. However, it never explicitly states when to prefer this over payment_get_list_payments or names any alternative. There are no exclusion conditions or prerequisites mentioned.

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.