Skip to main content
Glama

list_field_definitions

List all field definitions in a Laserfiche repository, including field names, types, multi-value support, and required status. Essential for preparing field-based queries or updates.

Instructions

List every field definition in the repository.

Use before authoring a field-based search query or preparing a field update — the response tells you which fields exist, their types (String, ShortInteger, List, Date, ...), whether they accept multi-value, whether they're required at the repository level, and (for List fields) the allowed values.

Independent fields and template-scoped fields are both returned. Combine with list_template_definitions to see which fields belong to which template.

Args: max_results: Page size (default 25, capped by LF_MAX_RESULTS_CEILING). skip: 0-indexed offset for pagination through large repositories. summary_only: If True, return only {count, names} instead of the full OData listing.

Returns: Server's raw OData listing with value (list of field definitions). Each item includes id, name, fieldType, isRequired, isMultiValue, listValues, defaultValue, length, constraint.

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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

Behavior4/5

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

Describes response structure (types, multi-value, allowed values), pagination parameters, summary_only behavior, and error format. No annotations provided, but description compensates well.

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?

Front-loaded with summary, organized into paragraphs and bullet points, no wasted words. Efficiently covers all necessary information.

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?

Thoroughly covers pagination, summary mode, output fields, and error response. Given output schema existence and parameter count, this is complete.

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 has 100% description coverage; description adds value by explaining default page size, capping, and the purpose of summary_only (avoiding large payloads).

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?

Clearly states 'List every field definition in the repository' with verb and resource. Distinguishes from sibling tools like get_template_fields by mentioning combination with list_template_definitions.

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?

Explicitly says 'Use before authoring a field-based search query or preparing a field update' and suggests combining with list_template_definitions. No explicit when-not-to-use but clear context.

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