Skip to main content
Glama

Lovie Company Formation

Create Document From User Template

documents_create_from_user_template

Create a finished document by filling a company user-uploaded template with collected field values. Does not modify the original upload.

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>",
      "userTemplateId": "<userTemplateId>"
    },
    "name": "documents_create_from_user_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNo
companyIdYesUUID value wrapper.
userTemplateIdYesUUID value wrapper.

Output Schema

NameRequiredDescriptionDefault
documentIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / fields / maxItems
      Previous value: -100New value: +500
  2. Changed4 schema fields changed
    • addedOutput schema / properties / documentId / anyOf
      Added value: +[
      +  {
      +    "description": "UUID value wrapper.",
      +    "properties": {
      +      "value": {
      +        "format": "uuid",
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • removedOutput schema / properties / documentId / description
      Removed value: -"UUID value wrapper."
    • removedOutput schema / properties / documentId / properties
      Removed value: -{
      -  "value": {
      -    "format": "uuid",
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / documentId / type
      Removed value: -"object"
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare openWorldHint=false and destructiveHint=false, so the safety profile is covered; the description adds a concrete guarantee that the original upload is not modified, which is more specific than the generic hint. It says nothing about failure behavior when field keys do not match template placeholders, but the output schema covers return values.

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, the action is front-loaded, and the non-destructiveness caveat follows immediately. Nothing is redundant or padded.

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 annotations and an output schema present, the essentials are covered, but for a creation tool with nested field objects it omits how field keys bind to template placeholders and whether a template must be resolved or pre-filled first. An agent could call it correctly but may mis-form the fields array on the first attempt.

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?

The description maps concepts to parameters — 'collected field values' to the fields array and 'company user-uploaded template' to userTemplateId — and the schema already documents the UUID wrappers, giving 67% coverage. It adds no detail on how field keys correspond to template placeholders or what happens with unmatched keys, so it does not meaningfully exceed 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?

The description gives a specific verb and resource: create a finished document by filling a company user-uploaded template with field values. The qualifier 'user-uploaded' distinguishes it from the sibling documents_create_document, which likely works from system templates, but no sibling is named explicitly.

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?

Usage is implied by the phrase 'company user-uploaded template' — the agent can infer this is the tool for user-supplied templates rather than built-in ones. However, there is no explicit when-to-use/when-not statement, no prerequisite (e.g. template must exist or be resolved first), and no named alternative.

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.