Lovie Company Formation

List Periods

accounting_get_list_periods

Read-only

GetListPeriods pages through a company's periods, newest first. Read-only.

Input Schema

TableJSON Schema

Name	Required	Description
`filter`	No
`pageSize`	No
`companyId`	Yes	UUID value wrapper.
`pageToken`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`periods`	No
`totalCount`	No
`nextPageToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed25 schema fields changedSep 10, 2026
- addedOutput schema / properties / periods / items / properties / closedAt / anyOf
```
Added value: +[
+  {
+    "format": "date-time",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / periods / items / properties / closedAt / format
```
Removed value: -"date-time"
```
- removedOutput schema / properties / periods / items / properties / closedAt / type
```
Removed value: -"string"
```
- addedOutput schema / properties / periods / items / properties / closedBy / anyOf
```
Added value: +[
+  {
+    "description": "UUID value wrapper.",
+    "properties": {
+      "value": {
+        "format": "uuid",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / periods / items / properties / closedBy / description
```
Removed value: -"UUID value wrapper."
```
- removedOutput schema / properties / periods / items / properties / closedBy / properties
```
Removed value: -{
-  "value": {
-    "format": "uuid",
-    "type": "string"
-  }
-}
```
- removedOutput schema / properties / periods / items / properties / closedBy / type
```
Removed value: -"object"
```
- addedOutput schema / properties / periods / items / properties / companyId / anyOf
```
Added value: +[
+  {
+    "description": "UUID value wrapper.",
+    "properties": {
+      "value": {
+        "format": "uuid",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / periods / items / properties / companyId / description
```
Removed value: -"UUID value wrapper."
```
- removedOutput schema / properties / periods / items / properties / companyId / properties
```
Removed value: -{
-  "value": {
-    "format": "uuid",
-    "type": "string"
-  }
-}
```
- removedOutput schema / properties / periods / items / properties / companyId / type
```
Removed value: -"object"
```
- addedOutput schema / properties / periods / items / properties / createdAt / anyOf
```
Added value: +[
+  {
+    "format": "date-time",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / periods / items / properties / createdAt / format
```
Removed value: -"date-time"
```
- removedOutput schema / properties / periods / items / properties / createdAt / type
```
Removed value: -"string"
```
- addedOutput schema / properties / periods / items / properties / currencies / items / properties / closingEntryId / anyOf
```
Added value: +[
+  {
+    "description": "UUID value wrapper.",
+    "properties": {
+      "value": {
+        "format": "uuid",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / periods / items / properties / currencies / items / properties / closingEntryId / description
```
Removed value: -"UUID value wrapper."
```
- removedOutput schema / properties / periods / items / properties / currencies / items / properties / closingEntryId / properties
```
Removed value: -{
-  "value": {
-    "format": "uuid",
-    "type": "string"
-  }
-}
```
- removedOutput schema / properties / periods / items / properties / currencies / items / properties / closingEntryId / type
```
Removed value: -"object"
```
- addedOutput schema / properties / periods / items / properties / id / anyOf
```
Added value: +[
+  {
+    "description": "UUID value wrapper.",
+    "properties": {
+      "value": {
+        "format": "uuid",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / periods / items / properties / id / description
```
Removed value: -"UUID value wrapper."
```
- removedOutput schema / properties / periods / items / properties / id / properties
```
Removed value: -{
-  "value": {
-    "format": "uuid",
-    "type": "string"
-  }
-}
```
- removedOutput schema / properties / periods / items / properties / id / type
```
Removed value: -"object"
```
- addedOutput schema / properties / periods / items / properties / updatedAt / anyOf
```
Added value: +[
+  {
+    "format": "date-time",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- removedOutput schema / properties / periods / items / properties / updatedAt / format
```
Removed value: -"date-time"
```
- removedOutput schema / properties / periods / items / properties / updatedAt / type
```
Removed value: -"string"
```
First observedAug 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds behavioral context beyond that: pagination ('pages through') and ordering ('newest first'). This is useful for an agent deciding whether to page through results or handle response ordering.

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 short sentences, front-loaded with the core action and ordering. The 'Read-only' note is redundant with annotations but harmless. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and annotations covering safety, the description is minimally adequate. However, it leaves filter behavior and pagination parameters unaddressed, and an agent must infer their meaning from the schema alone. Gaps remain for a fully informed call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25% (companyId has a minimal 'UUID value wrapper' note). The description barely helps: 'a company's periods' hints at companyId, but pageSize, pageToken, and filter semantics are left entirely unexplained. The description does not compensate for the low schema coverage.

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 uses a specific verb ('pages through') and resource ('a company's periods'), and adds a clear ordering detail ('newest first'). It is easily distinguished from single-period retrieval (accounting_get_period) and mutating period tools (accounting_close_period, accounting_reopen_period).

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 listing context is clear, but there is no explicit guidance about when to choose this over accounting_get_period or other period-related tools. The name and sibling list imply the distinction, but no direct routing or exclusion is stated.

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.