Skip to main content
Glama

Lovie Company Formation

Create Company

company_create_company

Creates a company owned by the signed-in user, for example before importing a cap table. Give its name (and code, a lowercase slug). The user becomes its owner; there is no way to create a company for someone else. Returns the new company id.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "company": "<company>"
    },
    "name": "company_create_company"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYes

Output Schema

NameRequiredDescriptionDefault
companyIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / company / properties / dunsCaseReference
      Added value: +{
      +  "maxLength": 100,
      +  "pattern": "^[A-Za-z0-9-]*$",
      +  "type": "string"
      +}
    • addedInput schema / properties / company / properties / dunsNumber
      Added value: +{
      +  "maxLength": 9,
      +  "pattern": "^([0-9]{9})?$",
      +  "type": "string"
      +}
    • changedInput schema / properties / company / properties / source / enum
      Previous value: -[
      -  "COMPANY_SOURCE_UNSPECIFIED",
      -  "COMPANY_SOURCE_LOVIE_FORMATION",
      -  "COMPANY_SOURCE_USER_CREATED",
      -  "COMPANY_SOURCE_IMPORTED"
      -]New value: +[
      +  "COMPANY_SOURCE_UNSPECIFIED",
      +  "COMPANY_SOURCE_LOVIE_FORMATION",
      +  "COMPANY_SOURCE_IMPORTED"
      +]
    • addedInput schema / properties / company / properties / websiteUrl
      Added value: +{
      +  "maxLength": 1000,
      +  "type": "string"
      +}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (which only declare non-destructive, closed-world), the description discloses ownership semantics — the caller becomes owner and cannot delegate — and that the new id is returned. It omits side effects like uniqueness/slug collisions and whether a duplicate name is rejected, but the mutation profile is well covered.

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?

Three short sentences: purpose and ownership first, then the key input guidance, then the return value. Nothing extraneous and no repetition of the schema.

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?

An output schema exists, so return values need no elaboration, and the annotations carry the safety profile. However, for a tool whose only parameter is a large nested object, the description leaves most creatable fields and the required userId unexplained, so an agent cannot tell which optional attributes are worth setting.

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 0% on a deeply nested company object with ~20 optional fields (ein, type, formedOn, address, aliases). The description only explains name and the lowercase-slug format for code; it says nothing about userId (which the schema marks required) or any of the optional attributes, so it only partially compensates for the coverage gap.

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 and resource ("Creates a company") plus the decisive scope fact that it is owned by the signed-in user, which separates it from company_get_company, company_update_company, and formation_create_formation. An agent can pick it without opening the schema.

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

Usage Guidelines4/5

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

"for example before importing a cap table" gives a concrete triggering scenario and the constraint "there is no way to create a company for someone else" rules out an expected misuse. It stops short of naming sibling alternatives or saying when to prefer formation flows instead.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.