Skip to main content
Glama

get_field_values

Retrieve template field values for a Laserfiche entry using its entry ID. Get metadata such as status, reviewer, or signing date.

Instructions

Read the template field values currently on an entry.

Use after you have an entry ID and need the metadata fields the user is asking about — e.g. "what's the status of this form?", "who's the assigned reviewer?", "when was this signed?". For the entry's own properties (name, type, path), use get_entry instead.

Args: entry_id: Integer entry ID.

Returns: {"values": [...]} — a list of field-value descriptors under the values key. Each item has field_name, values (always a list, even for single-value fields), field_type, is_multi_value, and is_required. Empty / unset fields are typically omitted by the Repository API rather than returned with empty values, so an empty list usually means the entry has no template assigned.

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?

The description fully details the return format, including the structure of each field descriptor and behavior for empty/unset fields. It also covers failure modes with common error slugs. However, it doesn't mention authorization or rate limits, but as a read operation with no annotations, the provided information is still substantial.

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 concise and well-structured: a one-line purpose, followed by usage guidance, examples, parameter definition, return format details, and error information. 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 simplicity (one parameter, output schema detailed in description), the description provides complete context. It covers when to use, what to expect in return, and error handling. The distinction from get_entry makes it contextually complete among siblings.

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?

The only parameter 'entry_id' is explained in the Args section as 'Integer entry ID', which combined with the context of needing an entry ID makes its purpose clear. While the schema itself has no description (0% coverage), the description compensates adequately, though it could be more explicit about what the ID refers to.

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 the tool reads template field values from an entry, with a specific verb 'Read' and resource 'template field values'. It distinguishes from sibling tool 'get_entry' by noting that for entry properties (name, type, path) one should use get_entry instead.

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?

The description explicitly tells when to use the tool: after having an entry ID and needing metadata fields. It gives example questions and directly advises against using it for entry properties, directing to get_entry 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