Skip to main content
Glama

Get Talonic Document

talonic_get_document
Read-only

Check a document's metadata and processing status by providing its document ID.

Instructions

Fetch a single document's metadata and processing status from the workspace.

USE WHEN: 'tell me about document X', or to poll status after talonic_request_upload until the file is ready. NOT FOR: full text (use talonic_to_markdown) · extracted fields (use talonic_extract). BY NAME: if the user names a file, call talonic_search first to get its document_id, then call this. ARGS: document_id. RETURNS: filename, pages, type_detected, language, and status. Status lifecycle: pending_upload -> queued -> extracting -> completed. Wait for completed before calling talonic_extract on a freshly uploaded doc. To read the document's text, call talonic_to_markdown with this id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
document_idYesThe Talonic document ID. Get this from a previous talonic_extract or talonic_search response.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
filenameNo
pagesNo
size_bytesNo
mime_typeNo
type_detectedNo
language_detectedNo
statusNo
sourceNo
triageNo
original_pathNo
extraction_countNo
latest_extraction_idNo
processing_logNo
created_atNo
linksNo
Behavior4/5

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

Annotations declare readOnlyHint=true and destructiveHint=false. The description adds context beyond annotations, detailing the status lifecycle and when to poll. However, it could further emphasize that this is a read-only operation, but it's clear from context.

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 well-structured with clear headings (USE WHEN, NOT FOR, BY NAME, ARGS, RETURNS) and is concise yet comprehensive. Every sentence serves a purpose.

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 present), the description covers all relevant aspects: input, output fields, status lifecycle, and related tools. It is complete for an agent to use correctly.

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?

The input schema fully describes the single parameter (document_id) with a note on its origin. The description repeats this ('ARGS: document_id') but does not add new semantic meaning beyond the schema. Schema coverage is 100%, so baseline 3 is appropriate.

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 'Fetch a single document's metadata and processing status from the workspace,' using a specific verb and resource. It distinguishes from siblings by noting 'NOT FOR: full text (use talonic_to_markdown) · extracted fields (use talonic_extract).'

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?

Explicit usage instructions are given: 'USE WHEN: tell me about document X, or to poll status...' and 'NOT FOR' with alternatives. It also explains how to get the document_id via talonic_search for user-named files.

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/talonicdev/talonic-mcp'

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