Skip to main content
Glama
Sign In
RootMind

RootMind

by cgaeking
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Document details

get_document_info
Read-onlyIdempotent

Retrieve a document's metadata—name, folder, path, type, size, page count, timestamps, and OCR status—to answer file-specific questions or verify it before reading its text.

Instructions

Get the details of one document without its text: file name, folder, path in the folder, type, file size, page/slide/sheet count, text length, created, modified and indexed time, and OCR state. Use it for questions about a file itself (how many pages, when it was changed, where it is) or to check a document before reading it; to read its text, use read_document. Read-only. Covers only the folders indexed by RootMind that this connection may access, as of the last indexing run (files changed since may be missing). Pass the doc_id from a search or list result. An unknown or inaccessible doc_id returns an error.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "doc_id": "<doc_id>"
    },
    "name": "get_document_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
doc_idYesDocument ID (32 hex characters, e.g. 3f2a...) exactly as returned by search_documents, search_fuzzy or list_documents.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.10.1
    • changedInput schema / properties / doc_id / description
      Previous value: -"Document ID, as returned by search_documents or list_documents."New value: +"Document ID (32 hex characters, e.g. 3f2a...) exactly as returned by search_documents, search_fuzzy or list_documents."
  2. Addedv2.10.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavior: coverage limited to RootMind-indexed folders this connection may access, staleness caveat ("as of the last indexing run (files changed since may be missing)"), and explicit error behavior for unknown or inaccessible doc_id. Only the return shape/pagination is left implicit, which keeps it from a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the resource and returned fields, then usage, then caveats — a sound order with no filler sentences. The long field enumeration is informative rather than wasteful, though the usage sentence and the read_document pointer could be merged to tighten it slightly.

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?

For a one-parameter, non-destructive lookup with no output schema, the description does the work the schema cannot: it enumerates the returned fields, states indexing/staleness limits, and specifies error behavior. An agent has everything needed to decide to call it and interpret a result.

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?

Schema coverage is 100% and the single doc_id parameter is fully documented in the schema, including the 32-hex-character format and where it comes from. The description's "Pass the doc_id from a search or list result" largely restates the schema; its only addition is the failure mode for an unknown id, so the baseline of 3 applies.

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?

States a specific verb and resource ("Get the details of one document") and immediately scopes it with "without its text," then enumerates the exact fields returned (name, folder, path, type, size, page count, timestamps, OCR state). This clearly separates it from read_document, which handles text.

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?

Gives explicit usage conditions ("questions about a file itself (how many pages, when it was changed, where it is)" and "check a document before reading it") and names the alternative with its selection condition: "to read its text, use read_document." The doc_id provenance requirement is also stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools