Lovie Company Formation

List Document Templates

document_template_list_templates

Read-only

List available legal document templates (YAML catalog).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No
`category`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`templates`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 10, 2026

addedOutput schema / properties / templates / items / properties / description / anyOf

Added value: +[
+  {
+    "description": "Free-form description (max 5000 chars).",
+    "properties": {
+      "value": {
+        "maxLength": 5000,
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / templates / items / properties / description / description
```
Removed value: -"Free-form description (max 5000 chars)."
```
removedOutput schema / properties / templates / items / properties / description / properties
```
Removed value: -{
-  "value": {
-    "maxLength": 5000,
-    "type": "string"
-  }
-}
```
removedOutput schema / properties / templates / items / properties / description / type
```
Removed value: -"object"
```

addedOutput schema / properties / templates / items / properties / title / anyOf

Added value: +[
+  {
+    "description": "Human-readable name (1-255 Unicode chars).",
+    "properties": {
+      "value": {
+        "maxLength": 255,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / templates / items / properties / title / description
```
Removed value: -"Human-readable name (1-255 Unicode chars)."
```

removedOutput schema / properties / templates / items / properties / title / properties

Removed value: -{
-  "value": {
-    "maxLength": 255,
-    "minLength": 1,
-    "type": "string"
-  }
-}

removedOutput schema / properties / templates / items / properties / title / type
```
Removed value: -"object"
```

First observedAug 11, 2026

TDQS

B3.1/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 the safety profile is covered. The description adds only that the result is a YAML catalog of available templates, which provides some context about the response form but does not explain filtering behavior, ordering, or response details.

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 with no redundant wording. Every word adds meaning, especially the '(YAML catalog)' qualifier.

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?

For a simple read-only listing tool with an output schema and safety annotations, the description is broadly adequate. However, the optional query and category parameters are left entirely unexplained, and there is no routing guidance relative to sibling document tools, so an agent is missing some context needed for fully correct use.

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 0%, and the description mentions neither 'query' nor 'category'. The parameter names are somewhat self-explanatory in the context of listing templates, but the description does not add meaning beyond the schema or clarify how the filters behave.

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 clearly states the action ('List') and the resource ('available legal document templates'), and the parenthetical '(YAML catalog)' adds specificity about what kind of listing this is. It is not a tautology, but it does not explicitly distinguish itself from sibling tools like documents_list_documents or documents_list_user_templates.

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, no exclusions, and no mention of when it is inappropriate. The description simply states what the tool does without helping an agent decide between this and closely related document/template listing siblings.

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.