Skip to main content
Glama

create_files

Create up to 200 markdown or mermaid files in one batch call, with automatic folder creation and per-item error isolation. Use for bulk file ingestion.

Instructions

Batch variant of create_file — create up to 200 markdown or mermaid files in one call. Each item follows the same rules (project_id required if destination is project or kontexta). SIDE EFFECTS: writes new files to disk and inserts FTS5 rows; missing folders are mkdir'd. Per-item failures are isolated to errors[] and the rest of the batch still commits — partial success is the norm, always inspect error_count. No external auth or rate limits. Returns {created_count, error_count, created, errors}. Use for bulk ingestion; for >200 items, page yourself. Pass format='mmd' on an item to create a Mermaid diagram file (.mmd); defaults to 'md'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filesYesFiles to create (max 200 per call)
Behavior5/5

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

With no annotations, the description fully covers behavioral traits: side effects (writes to disk, FTS5 inserts, mkdir), partial success semantics (`errors[]`, `error_count`), return structure, and absence of auth/rate limits. This is exceptionally transparent.

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?

The description is a single, well-structured paragraph that front-loads purpose, then covers constraints, behavior, and return values. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (batch creation with partial success, multiple parameters, no output schema), the description covers all necessary context: how to use, what to expect, error handling, and return format. No gaps remain.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds meaning by explaining the `format` parameter (.md vs .mmd), the conditional requirement of `project_id`, and the batch limit of 200. This goes beyond the schema's minimal descriptions.

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?

The description clearly identifies the tool as a batch variant of `create_file`, specifies it creates up to 200 markdown or mermaid files, and mentions the key constraint of batch size. This distinguishes it from the sibling `create_file` and other tools.

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?

The description advises 'Use for bulk ingestion' and for '>200 items, page yourself', implying when to use. It also notes the `project_id` requirement for certain destinations. However, it does not explicitly state when to prefer the singular `create_file` instead, which is a minor gap.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/safiyu/kontexta'

If you have feedback or need assistance with the MCP directory API, please join our Discord server