Skip to main content
Glama

DocImprint

by com.docimprint.api
OverviewDiscussionsAdmin

Create Collection

create_collection

Create a named document collection for cross-document semantic search and RAG-based Q&A. Free — no credits consumed. Use when you want to group related evidence bundles for unified search (search_collection) or question answering (ask_collection). NOTE: Collections start empty. Add evidence bundles with add_document_to_collection. Indexing is async — once complete, use search_collection or ask_collection. Returns: { collection_id: string (col_...), name: string } Example prompts:

  • "Create a collection called Q4 Contracts for my quarterly reports."

  • "Set up a new document group named Due Diligence Docs."

  • "Make a collection to organize my vendor agreements."

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesHuman-readable collection name. Example: "Q4 Contracts" or "Due Diligence Docs"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
collection_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "collection_id": {
+      "type": "string"
+    },
+    "name": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "collection_id",
+    "name"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Human-readable collection name, e.g. \"Q4 Contracts\" or \"Due Diligence Docs\""New value: +"Human-readable collection name. Example: \"Q4 Contracts\" or \"Due Diligence Docs\""
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With annotations covering the safety profile, the description still adds useful behavior: no credits consumed, collection starts empty, and indexing is asynchronous with search/ask available only after completion. It omits whether repeating the same name creates a duplicate despite idempotentHint=false being called out in the annotations.

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?

Front-loaded with the core purpose, then NOTE/Returns/example sections in a scannable order. The three example prompts are somewhat repetitive and could be trimmed, but each section earns its place and nothing is buried.

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?

Covers the creation-to-search lifecycle and repeats the return shape, which is useful even though an output schema exists. The only meaningful gap is name uniqueness/duplicate-creation behavior, which is left ambiguous for a non-idempotent create.

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 coverage is 100% and the single 'name' parameter is already documented with an example format, so the schema carries the semantics. The description's example prompts reinforce naming style but add no constraints or format rules beyond what the schema provides; baseline 3 applies.

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 (create) and resource (named document collection) and scopes it to cross-document semantic search and RAG Q&A. It names the sibling tools it feeds into (search_collection, ask_collection) and the sibling that populates it (add_document_to_collection), so it is distinguishable from them without opening either schema.

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

Usage Guidelines5/5

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

Explicitly says when to use it: 'Use when you want to group related evidence bundles for unified search ... or question answering.' It also names the alternative downstream tools and the prerequisite step (add_document_to_collection), leaving no inference needed.

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

All DocImprint toolsInspect
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.

Resources