Lovie Company Formation

Get Formation Info

formation_get_formation_info

Read-only

GetFormationInfo returns educational content topics or content for a specific topic

Input Schema

TableJSON Schema

Name	Required	Description	Default
`topic`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`topic`	No
`topics`	No
`content`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 10, 2026

addedOutput schema / properties / topics / 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 / topics / items / properties / description / description
```
Removed value: -"Free-form description (max 5000 chars)."
```
removedOutput schema / properties / topics / items / properties / description / properties
```
Removed value: -{
-  "value": {
-    "maxLength": 5000,
-    "type": "string"
-  }
-}
```
removedOutput schema / properties / topics / items / properties / description / type
```
Removed value: -"object"
```

addedOutput schema / properties / topics / items / properties / name / 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 / topics / items / properties / name / description
```
Removed value: -"Human-readable name (1-255 Unicode chars)."
```

removedOutput schema / properties / topics / items / properties / name / properties

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

removedOutput schema / properties / topics / items / properties / name / type
```
Removed value: -"object"
```

First observedAug 11, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already cover read-only/non-destructive behavior, so the description only needs to add context. The phrase 'topics or content for a specific topic' usefully conveys that the result changes depending on whether a topic is supplied, though it adds no deeper context about pagination or empty results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence with no filler, and the main behavior is front-loaded. The phrase 'GetFormationInfo returns' is slightly redundant with the title, but the sentence is otherwise tight.

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 one-optional-param read-only tool with an output schema, this is mostly workable. Missing usage guidance and a clearer statement of the omitted-topic default keep it from being fully self-sufficient.

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?

With 0% schema description coverage, the description should carry parameter meaning, but it only loosely maps 'topic' to 'a specific topic' and does not explicitly explain that omitting the topic returns the list of topics. Pattern and optionality constraints are left entirely to the schema.

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?

States a specific verb ('returns') and resource ('educational content topics or content for a specific topic'), and the optional topic parameter makes the two modes understandable. It doesn't explicitly differentiate from formation_get_formation or formation_get_formation_timeline among siblings.

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?

No guidance on when to call this tool vs alternatives; no exclusions or prerequisites. The description only defines behavior and never says 'use this when...'.

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.