Skip to main content
Glama

Get Talonic Document

talonic_get_document
Read-only

Fetch full metadata for a document in your Talonic workspace using its document ID. Get details like filename, page count, type, language, and processing log.

Instructions

STATUS: stable.

Fetch full metadata for a single document already in the user's Talonic workspace. Returns id, filename, page count, detected document type, language, processing log, and link URLs (self, extractions, dashboard).

USE WHEN:

  • You need details about a specific document the user already extracted or uploaded.

  • You have a document_id from a previous extract or search call and want more context.

  • The user asks 'tell me about document X' or similar.

DO NOT USE WHEN:

  • The user wants the document's full text content (use talonic_to_markdown for OCR markdown).

  • The user wants extracted structured data (use talonic_extract with a schema, or fetch the extraction by id).

  • The user has a file but no document_id yet (call talonic_extract first to ingest the document).

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 provide readOnlyHint and openWorldHint, but description adds context: stability status, list of returned metadata fields, and that it does not return full text or extractions. No contradiction with annotations.

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 clear sections, no fluff, and every sentence adds value. Front-loaded with status and core action.

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 output schema exists, description adequately covers purpose, parameters, and exclusions. All sibling tools referenced for alternative cases. Complete for a fetch-by-id tool.

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?

Single parameter document_id is described in schema with clear source ('from previous extract or search'), and description reinforces this in usage guidelines. Schema coverage is 100%, so baseline is 3, but added context raises it to 4.

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 explicitly states 'Fetch full metadata for a single document' and lists returned fields (id, filename, etc.), clearly distinguishing it from siblings like talonic_to_markdown (full text) and talonic_extract (ingestion).

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?

Provides explicit 'USE WHEN' and 'DO NOT USE WHEN' sections with concrete cases (e.g., having a document_id, needing markdown vs metadata), and names alternative tools directly.

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