Lovie Company Formation

Get EIN Filing Info

formation_get_ein_filing_info

Read-only

GetEinFilingInfo returns the stored payload without the SSN/ITIN.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description	Default
`info`	No
`hasSsn`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 10, 2026

addedOutput schema / properties / info / anyOf

Added value: +[
+  {
+    "properties": {
+      "appliedForEinBefore": {
+        "type": "boolean"
+      },
+      "closingMonth": {
+        "type": "integer"
+      },
+      "dateOfBirth": {
+        "type": "string"
+      },
+      "employeesAgricultural": {
+        "type": "integer"
+      },
+      "employeesHousehold": {
+        "type": "integer"
+      },
+      "employeesOther": {
+        "type": "integer"
+      },
+      "firstWagesDate": {
+        "type": "string"
+      },
+      "previousEin": {
+        "type": "string"
+      },
+      "principalActivity": {
+        "type": "string"
+      },
+      "reasonForApplying": {
+        "enum": [
+          "EIN_REASON_FOR_APPLYING_UNSPECIFIED",
+          "EIN_REASON_FOR_APPLYING_STARTED_NEW_BUSINESS",
+          "EIN_REASON_FOR_APPLYING_HIRED_EMPLOYEES",
+          "EIN_REASON_FOR_APPLYING_BANKING_PURPOSE",
+          "EIN_REASON_FOR_APPLYING_CHANGED_ORGANIZATION_TYPE",
+          "EIN_REASON_FOR_APPLYING_PURCHASED_GOING_BUSINESS",
+          "EIN_REASON_FOR_APPLYING_CREATED_A_TRUST",
+          "EIN_REASON_FOR_APPLYING_CREATED_A_PENSION_PLAN",
+          "EIN_REASON_FOR_APPLYING_COMPLIANCE",
+          "EIN_REASON_FOR_APPLYING_OTHER"
+        ],
+        "type": "string"
+      },
+      "submittedAt": {
+        "anyOf": [
+          {
+            "format": "date-time",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "submittedVia": {
+        "enum": [
+          "EIN_SUBMITTED_VIA_UNSPECIFIED",
+          "EIN_SUBMITTED_VIA_DASHBOARD",
+          "EIN_SUBMITTED_VIA_MCP"
+        ],
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / info / properties

Removed value: -{
-  "appliedForEinBefore": {
-    "type": "boolean"
-  },
-  "closingMonth": {
-    "type": "integer"
-  },
-  "dateOfBirth": {
-    "type": "string"
-  },
-  "employeesAgricultural": {
-    "type": "integer"
-  },
-  "employeesHousehold": {
-    "type": "integer"
-  },
-  "employeesOther": {
-    "type": "integer"
-  },
-  "firstWagesDate": {
-    "type": "string"
-  },
-  "previousEin": {
-    "type": "string"
-  },
-  "principalActivity": {
-    "type": "string"
-  },
-  "reasonForApplying": {
-    "enum": [
-      "EIN_REASON_FOR_APPLYING_UNSPECIFIED",
-      "EIN_REASON_FOR_APPLYING_STARTED_NEW_BUSINESS",
-      "EIN_REASON_FOR_APPLYING_HIRED_EMPLOYEES",
-      "EIN_REASON_FOR_APPLYING_BANKING_PURPOSE",
-      "EIN_REASON_FOR_APPLYING_CHANGED_ORGANIZATION_TYPE",
-      "EIN_REASON_FOR_APPLYING_PURCHASED_GOING_BUSINESS",
-      "EIN_REASON_FOR_APPLYING_CREATED_A_TRUST",
-      "EIN_REASON_FOR_APPLYING_CREATED_A_PENSION_PLAN",
-      "EIN_REASON_FOR_APPLYING_COMPLIANCE",
-      "EIN_REASON_FOR_APPLYING_OTHER"
-    ],
-    "type": "string"
-  },
-  "submittedAt": {
-    "format": "date-time",
-    "type": "string"
-  },
-  "submittedVia": {
-    "enum": [
-      "EIN_SUBMITTED_VIA_UNSPECIFIED",
-      "EIN_SUBMITTED_VIA_DASHBOARD",
-      "EIN_SUBMITTED_VIA_MCP"
-    ],
-    "type": "string"
-  }
-}

removedOutput schema / properties / info / type
```
Removed value: -"object"
```

First observedAug 11, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true, so the description doesn't need to restate safety. It adds meaningful behavioral context by disclosing that the returned payload excludes SSN/ITIN, which is a privacy-relevant behavior beyond what the annotations convey.

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?

A single sentence with no filler. It front-loads the action, identifies the resource, and includes the key redaction caveat without wasting words.

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?

For a one-parameter read-only tool with an output schema and safety annotations, the description is largely sufficient. The main missing piece is usage guidance relative to related formation tools, but the core invocation details are covered.

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%, and the sole parameter is documented as a UUID value wrapper. The description adds little semantic detail about formationId beyond its role in the read operation, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action—return the stored EIN filing payload—and adds the important redaction detail that SSN/ITIN are excluded. It does not explicitly contrast with sibling tools like formation_submit_ein_filing_info, but the title and verb make the tool's role clear.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives. The agent must infer that it is the read counterpart to formation_submit_ein_filing_info, and no conditions, prerequisites, or exclusions are provided.

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.