Skip to main content
Glama

Instantiate Template Natively

instantiate_template_native

Create new documents from templates using native block cloning with variable substitutions, falling back to markdown only when necessary.

Instructions

Instantiate a template using native AFFiNE block cloning when supported, falling back to markdown materialization only when necessary.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdNo
templateDocIdYesThe template doc to instantiate.
titleNoOptional title for the new document. Defaults to the template title.
variablesNoKey-value map of {{variable}} substitutions applied during cloning.
parentDocIdNoOptional parent doc to link the instantiated doc under in the sidebar.
allowFallbackNoIf false, fail instead of falling back to markdown materialization when native cloning is unsupported.
preserveTagsNoIf true (default), copy the template's tags onto the instantiated doc.
Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses the fallback behavior (native cloning then markdown) but does not mention side effects, authentication needs, or whether the original template is modified.

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?

The description is a single sentence, concise and front-loaded. It avoids verbosity but could include more detail without sacrificing brevity.

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

Completeness2/5

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

With 7 parameters, no output schema, and no annotations, the description is incomplete. It does not explain return values, error conditions, or the nature of the fallback, leaving important gaps for an AI agent.

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 86%, with only workspaceId lacking a description. The description adds no additional meaning beyond the schema. Baseline 3 is appropriate.

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 clearly states the tool instantiates a template using native AFFiNE block cloning with fallback. The verb 'instantiate' and resource 'template' are specific, but it does not distinguish from sibling tools like 'create_doc' or 'create_doc_from_markdown'.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives such as 'create_doc' or 'inspect_template_structure'. No prerequisites, context, or exclusion criteria are provided.

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/DAWNCR0W/affine-mcp-server'

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