Skip to main content
Glama

list_template_definitions

List all template definitions in a Laserfiche repository to discover available templates before assigning them. Supports filtering by name, pagination, and a summary-only mode for quick lookups.

Instructions

List template definitions in the repository.

Use to discover which templates exist before calling assign_template. Pass template_name to fetch a single template by name (the same listing, filtered server-side).

Args: template_name: If set, return only the template with this exact name. Case-sensitive on most builds. max_results: Page size (default 25, capped by LF_MAX_RESULTS_CEILING). skip: 0-indexed offset for pagination. summary_only: If True, return only {count, names}.

Returns: Server's raw OData listing with value. Each item has id, name, displayName, description, fieldCount, and color. This response does NOT enumerate the fields ON the template — use list_field_definitions to inspect those (they're the ones with isRequired=true when scoped to the template).

On failure: returns {"mode": "error", "error": <slug>, ...}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
template_nameNoIf set, return only the template with this exact name. Case-sensitive on most builds.
max_resultsNoPage size (default 25, capped by LF_MAX_RESULTS_CEILING).
skipNo0-indexed offset for pagination through large repositories.
summary_onlyNoWhen True, return only {count, names} instead of the full OData listing — useful for 'what's available?' lookups that would otherwise return 30-50 KB of definition payload.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations are provided, so the description must fully disclose behavior. It does so by explaining pagination (skip, max_results), the summary_only mode, error format, and that the response does not include field definitions.

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 well-structured with a brief intro, parameter documentation, and return/failure details. It is detailed but not excessively long, though some redundancy exists (e.g., repeating max_results default).

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 has 4 parameters, no required ones, and an output schema, the description covers all necessary aspects: purpose, parameter usage, response shape, failure mode, and relationship to other tools like list_field_definitions.

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%, baseline is 3. The description adds value by elaborating on each parameter: template_name's server-side filtering and case-sensitivity, max_results cap, skip offset, and summary_only's use case.

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 states 'List template definitions in the repository' and positions the tool as a discovery step before calling assign_template. It distinguishes from siblings like list_field_definitions by explaining what the tool does not return (fields).

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 explicitly tells when to use ('discover which templates exist before calling assign_template') and for each parameter explains its effect. It does not explicitly state when not to use, but the context is clear enough.

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/SamuelSHernandez/laserfiche-mcp'

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