Skip to main content
Glama

Lovie Company Formation

List User Templates

documents_list_user_templates
Read-only

List company-scoped user-uploaded templates (Use your own template). Separate from Lovie's builtin catalog.

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": {
      "companyId": "<companyId>"
    },
    "name": "documents_list_user_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
templatesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedOutput schema / properties / templates / items / properties / boxes
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "cover": {
      +        "type": "boolean"
      +      },
      +      "height": {
      +        "type": "number"
      +      },
      +      "id": {
      +        "type": "string"
      +      },
      +      "key": {
      +        "type": "string"
      +      },
      +      "kind": {
      +        "enum": [
      +          "USER_TEMPLATE_BOX_KIND_UNSPECIFIED",
      +          "USER_TEMPLATE_BOX_KIND_VALUE",
      +          "USER_TEMPLATE_BOX_KIND_SIGNATURE",
      +          "USER_TEMPLATE_BOX_KIND_DATE"
      +        ],
      +        "type": "string"
      +      },
      +      "label": {
      +        "type": "string"
      +      },
      +      "maxLen": {
      +        "type": "integer"
      +      },
      +      "options": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "pageIndex": {
      +        "type": "integer"
      +      },
      +      "pdfFieldName": {
      +        "type": "string"
      +      },
      +      "required": {
      +        "type": "boolean"
      +      },
      +      "slot": {
      +        "type": "string"
      +      },
      +      "source": {
      +        "type": "string"
      +      },
      +      "type": {
      +        "type": "string"
      +      },
      +      "width": {
      +        "type": "number"
      +      },
      +      "x": {
      +        "type": "number"
      +      },
      +      "y": {
      +        "type": "number"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / templates / items / properties / pages
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "height": {
      +        "type": "number"
      +      },
      +      "rotate": {
      +        "type": "integer"
      +      },
      +      "width": {
      +        "type": "number"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / templates / items / properties / previousVersionId
      Added value: +{
      +  "anyOf": [
      +    {
      +      "description": "UUID value wrapper.",
      +      "properties": {
      +        "value": {
      +          "format": "uuid",
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / templates / items / properties / status
      Added value: +{
      +  "enum": [
      +    "COMPANY_USER_TEMPLATE_STATUS_UNSPECIFIED",
      +    "COMPANY_USER_TEMPLATE_STATUS_LEGACY",
      +    "COMPANY_USER_TEMPLATE_STATUS_DRAFT",
      +    "COMPANY_USER_TEMPLATE_STATUS_READY",
      +    "COMPANY_USER_TEMPLATE_STATUS_ONE_TIME"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / templates / items / properties / version
      Added value: +{
      +  "type": "integer"
      +}
  2. Changed1 schema field changed
    • changedOutput schema / properties / templates / items / properties / detectedCategory / enum
      Previous value: -[
      -  "DOCUMENT_CATEGORY_UNSPECIFIED",
      -  "DOCUMENT_CATEGORY_EMPLOYMENT",
      -  "DOCUMENT_CATEGORY_EQUITY",
      -  "DOCUMENT_CATEGORY_COMPANY",
      -  "DOCUMENT_CATEGORY_TRANSACTION",
      -  "DOCUMENT_CATEGORY_GENERAL",
      -  "DOCUMENT_CATEGORY_STATE",
      -  "DOCUMENT_CATEGORY_IRS"
      -]New value: +[
      +  "DOCUMENT_CATEGORY_UNSPECIFIED",
      +  "DOCUMENT_CATEGORY_EMPLOYMENT",
      +  "DOCUMENT_CATEGORY_EQUITY",
      +  "DOCUMENT_CATEGORY_COMPANY",
      +  "DOCUMENT_CATEGORY_TRANSACTION",
      +  "DOCUMENT_CATEGORY_GENERAL",
      +  "DOCUMENT_CATEGORY_STATE",
      +  "DOCUMENT_CATEGORY_IRS",
      +  "DOCUMENT_CATEGORY_STATEMENT"
      +]
  3. Changed1 schema field changed
    • changedOutput schema / properties / templates / items / properties / detectedCategory / enum
      Previous value: -[
      -  "DOCUMENT_CATEGORY_UNSPECIFIED",
      -  "DOCUMENT_CATEGORY_EMPLOYMENT",
      -  "DOCUMENT_CATEGORY_EQUITY",
      -  "DOCUMENT_CATEGORY_COMPANY",
      -  "DOCUMENT_CATEGORY_TRANSACTION",
      -  "DOCUMENT_CATEGORY_GENERAL"
      -]New value: +[
      +  "DOCUMENT_CATEGORY_UNSPECIFIED",
      +  "DOCUMENT_CATEGORY_EMPLOYMENT",
      +  "DOCUMENT_CATEGORY_EQUITY",
      +  "DOCUMENT_CATEGORY_COMPANY",
      +  "DOCUMENT_CATEGORY_TRANSACTION",
      +  "DOCUMENT_CATEGORY_GENERAL",
      +  "DOCUMENT_CATEGORY_STATE",
      +  "DOCUMENT_CATEGORY_IRS"
      +]
  4. Changed16 schema fields changed
    • addedOutput schema / properties / templates / items / properties / companyId / anyOf
      Added value: +[
      +  {
      +    "description": "UUID value wrapper.",
      +    "properties": {
      +      "value": {
      +        "format": "uuid",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / templates / items / properties / companyId / description
      Removed value: -"UUID value wrapper."
    • removedOutput schema / properties / templates / items / properties / companyId / properties
      Removed value: -{
      -  "value": {
      -    "format": "uuid",
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / templates / items / properties / companyId / type
      Removed value: -"object"
    • addedOutput schema / properties / templates / items / properties / createdAt / anyOf
      Added value: +[
      +  {
      +    "format": "date-time",
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / templates / items / properties / createdAt / format
      Removed value: -"date-time"
    • removedOutput schema / properties / templates / items / properties / createdAt / type
      Removed value: -"string"
    • addedOutput schema / properties / templates / items / properties / createdByUserId / anyOf
      Added value: +[
      +  {
      +    "description": "UUID value wrapper.",
      +    "properties": {
      +      "value": {
      +        "format": "uuid",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / templates / items / properties / createdByUserId / description
      Removed value: -"UUID value wrapper."
    • removedOutput schema / properties / templates / items / properties / createdByUserId / properties
      Removed value: -{
      -  "value": {
      -    "format": "uuid",
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / templates / items / properties / createdByUserId / type
      Removed value: -"object"
    • addedOutput schema / properties / templates / items / properties / fields / items / properties / choices
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedOutput schema / properties / templates / items / properties / id / anyOf
      Added value: +[
      +  {
      +    "description": "UUID value wrapper.",
      +    "properties": {
      +      "value": {
      +        "format": "uuid",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / templates / items / properties / id / description
      Removed value: -"UUID value wrapper."
    • removedOutput schema / properties / templates / items / properties / id / properties
      Removed value: -{
      -  "value": {
      -    "format": "uuid",
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / templates / items / properties / id / type
      Removed value: -"object"
  5. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the company-scoping constraint and that results are user-uploaded rather than builtin, which is genuinely useful context, but nothing about pagination, ordering, or empty-result behavior.

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?

Two short sentences, front-loaded with the verb and resource, no filler. The parenthetical '(Use your own template)' is UI copy that adds little, but overall it is tight.

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?

A single required parameter fully documented in the schema, an output schema present, and read-only annotations mean this simple list tool needs little more. The description is adequate, with only the unnamed catalog sibling as a modest gap.

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?

There is only one parameter (companyId) and schema description coverage is 100%, so the schema already carries the burden; baseline 3 applies. 'Company-scoped' loosely implies the companyId's role but adds no format or constraint detail beyond the schema's UUID wrapper.

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?

Names a specific verb (List) and resource (company-scoped user-uploaded templates) and adds a scope qualifier that separates it from the builtin catalog. It does not name the sibling that serves the builtin catalog, so differentiation is conceptual rather than explicit.

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 phrase 'Separate from Lovie's builtin catalog' implies the alternative and when to pick this one, but the alternative tool is never named and there is no explicit when-not guidance. Usage is inferable rather than stated.

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.