InvoiceVista Invoice Maker

Check InvoiceVista plan and limits

get_subscription

Read-onlyIdempotent

Use this when someone asks which InvoiceVista plan a business is on, or how many customers, invoices or users it allows. Returns the active or past-due plan's name, status, billing frequency and limits, or the Free plan's defaults when there is none. Not for customer invoices or payments.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`businessId`	Yes	Business id: 24 lowercase hexadecimal characters

Output Schema

TableJSON Schema

Name	Required	Description	Default
`status`	Yes
`subscription`	Yes	Plan entitlements; limits are caps, not usage. Payment-processor identifiers and credentials are never returned.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026

changedOutput schema / properties / subscription / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "billingFrequency": {
-        "anyOf": [
-          {
-            "enum": [
-              "MONTHLY",
-              "YEARLY"
-            ],
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "maxNumberOfCustomers": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "maxNumberOfInvoices": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "maxNumberOfReminders": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "maxNumberOfUsers": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "productName": {
-        "anyOf": [
-          {
-            "maxLength": 200,
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "status": {
-        "anyOf": [
-          {
-            "enum": [
-              "ACTIVE",
-              "PAST_DUE",
-              "CANCELED"
-            ],
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "required": [
-      "status",
-      "productName",
-      "billingFrequency",
-      "maxNumberOfCustomers",
-      "maxNumberOfInvoices",
-      "maxNumberOfReminders",
-      "maxNumberOfUsers"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "billingFrequency": {
+        "anyOf": [
+          {
+            "enum": [
+              "MONTHLY",
+              "YEARLY"
+            ],
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "maxNumberOfCustomers": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "maxNumberOfInvoices": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "maxNumberOfUsers": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "productName": {
+        "anyOf": [
+          {
+            "maxLength": 200,
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "status": {
+        "anyOf": [
+          {
+            "enum": [
+              "ACTIVE",
+              "PAST_DUE",
+              "CANCELED"
+            ],
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "required": [
+      "status",
+      "productName",
+      "billingFrequency",
+      "maxNumberOfCustomers",
+      "maxNumberOfInvoices",
+      "maxNumberOfUsers"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed2 schema fields changedSep 30, 2026

changedInput schema / properties / businessId / description

Previous value: -"24-character lowercase hexadecimal business id"New value: +"Business id: 24 lowercase hexadecimal characters"

addedOutput schema / properties / subscription / description

Added value: +"Plan entitlements; limits are caps, not usage. Payment-processor identifiers and credentials are never returned."

First observedSep 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds real behavioral context beyond that: it returns the active OR past-due plan, and falls back to Free plan defaults when no plan exists — a non-obvious edge case an agent would otherwise have to discover at runtime.

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?

Two sentences with zero filler: usage trigger first, return contract and boundary second. Every clause earns its place, and nothing is buried.

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?

An output schema exists, so return-shape detail is already structured; the description still summarizes the useful cases (active, past-due, no-plan fallback). With a single well-documented parameter and full annotation coverage, nothing needed to call this 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?

Only one parameter, and schema coverage is 100% — the schema documents businessId including its 24-hex-character pattern. The description adds nothing about the parameter, so the baseline 3 applies when structured data does all the work.

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 (retrieve the InvoiceVista subscription plan for a business) and enumerates exactly what it yields: plan name, status, billing frequency and limits. The closing sentence distinguishes it from sibling reporting tools by ruling out customer invoices and payments.

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?

Opens with an explicit trigger ('Use this when someone asks which plan a business is on, or how many customers, invoices or users it allows') and adds an explicit exclusion ('Not for customer invoices or payments'). Both when-to-use and when-not-to-use are present, so 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 InvoiceVista Invoice Maker 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.

Resources

Need Help?