Retrieve metadata for a Tealfabric document or file using its full path to inspect storage details before managing or processing it.
Get metadata for a document/file in Tealfabric documents storage.
| Name | Required | Description | Default |
|---|---|---|---|
| file_path | Yes | Full path to the file (e.g. packages/report-v1.zip) | |
| tenant_id | No | Ignored by the API; auth tenant wins. Kept for backward compatibility. |
Changes observed during successful MCP inspections.
v0.2.0Input schema / additionalPropertiesRemoved value: -falseInput schema / properties / tenant_id / descriptionPrevious value: -"Tenant ID (defaults to authenticated tenant)"New value: +"Ignored by the API; auth tenant wins. Kept for backward compatibility."v0.1.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral disclosure burden. It only implies a read operation and does not state permission requirements, behavior for missing files, or what metadata is returned.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single front-loaded sentence with no wasted text. It is appropriately concise, though it lacks any additional structure or differentiating detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations, no output schema, and no description of returned metadata or error behavior, the definition is too thin for an agent to understand the tool's full behavior. The parameters are well documented, but the description does not compensate for the missing behavioral context.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, including the required file_path and the optional tenant_id parameter. The description adds no parameter-level meaning beyond the schema, so the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
It states a specific verb ('Get') and resource ('metadata for a document/file'), making the basic operation clear. It does not explicitly differentiate itself from sibling tools such as tealfabric_read_document_text, tealfabric_list_document_tree, or tealfabric_download_document.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no guidance on when to use this tool versus related document tools. It does not mention alternatives, prerequisites, or exclusions, so an agent must infer selection from the tool name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.