Skip to main content
Glama

laserfiche_entry_get

Retrieve metadata for a Laserfiche entry by its ID. Returns name, type, path, parent ID, template, page count, and timestamps.

Instructions

Fetch metadata for a single entry by ID.

Use this once you have an entry ID (from search, list_folder, or get_entry_by_path) and need the entry's full metadata: name, type (Folder vs Document), full path, parent ID, template name, page count (for paginated documents), and timestamps.

This does NOT return field values — for those, call get_field_values. This does NOT return document content — for that, call get_document_edoc (mode="text" for extracted text, mode="bytes" for the raw file).

Args: entry_id: Integer entry ID.

Returns: EntryDetail (id, name, entry_type, parent_id, full_path, template_name, page_count, is_electronic_document, extension, creation time, last modified time).

On failure: returns {"mode": "error", "error": <slug>, "entry_id": <int>, ...}. Common slugs: not_found, auth_failed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entry_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations provided, the description mentions it retrieves metadata (read-only behavior), specifies the return fields, and describes error response format. It does not explicitly mention side effects or authentication, but the read-only nature is clear.

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?

Well-structured with a clear first sentence, then usage context, explicit exclusions, and a concise args/returns section. Every sentence adds value, and it is appropriately sized for the tool's simplicity.

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 a single parameter, no annotations, but presence of output schema, the description covers purpose, usage, parameter, return fields, and error conditions comprehensively. No gaps remain.

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?

Despite 0% schema description coverage, the description mentions the sole parameter 'entry_id' as 'Integer entry ID.' This adds minimal information over the schema type definition; however, since there is only one simple parameter, it is adequate.

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 'Fetch metadata for a single entry by ID' with explicit verb and resource. Distinguishes from sibling tools by noting it does not return field values (call get_field_values) or document content (call get_document_edoc).

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 states when to use: after obtaining an entry ID from search, list_folder, or get_entry_by_path. Also provides explicit guidance on what not to use it for and which alternative tools to call instead.

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