Skip to main content
Glama

Get one of my documents

document_get
Read-onlyIdempotent

Details of one of your own documents by ref: folder, kind, source, status, size, dates and whether it can be downloaded. Someone else's ref returns not found. Free text is wrapped as data.

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": {
      "ref": "<ref>"
    },
    "name": "document_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
refYesDocument ref (from documents_list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world behavior, so the description's job is to add context, and it does: ownership scoping (foreign refs yield not found) and the safety note that free text is wrapped as data, which warns the agent against treating returned content as instructions. It stops short of describing the response envelope or error shape, which is acceptable given the low-risk read profile.

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?

Three short sentences with no filler: the field list is front-loaded, the ownership/not-found rule follows, and the injection-safety note closes. Every clause carries information an agent can act on.

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 single-parameter read tool with no output schema, the description supplies the field inventory, the ownership constraint, the not-found outcome and the data-wrapping caveat. Nothing essential to calling it correctly is missing.

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?

Schema coverage is 100% and the ref pattern plus 'from documents_list' origin are already documented, so the baseline would be 3. The description adds genuine meaning by tying ref validity to ownership, telling the agent that a well-formed ref outside its scope will resolve to not found rather than an error.

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 details of a document) plus an explicit ownership scope ('one of your own documents by ref'), and enumerates the fields returned. This makes it clearly distinct from listing tools like documents_list and from document_download_link, since it only reports whether download is possible.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: the ref-keyed lookup and the note that another person's ref returns not found tell the agent this is for single-document retrieval within its own scope. There is no explicit 'use documents_list first to obtain a ref' instruction in the description (only in the schema) and no explicit pointer to document_download_link for fetching the file itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources