Skip to main content
Glama

Get Project Structure

get_structure
Read-onlyIdempotent

Retrieve the binder hierarchy of an open Scrivener project, listing folders and documents with IDs, titles, types, depths, and word counts to understand the manuscript layout and obtain document identifiers for subsequent tools.

Instructions

Return the binder hierarchy of the open project: its folders and documents in tree order, each with id, title, type, depth, and word count. Use this to understand the manuscript layout and to obtain the document ids that read_document, write_document, and the analysis tools require. By default returns a compact flat array of [id, title, type, depth, wordCount, hasChildren] tuples to save tokens; set summaryOnly for just project-level counts. Requires an open project (call open_project first).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
flatNoWhen true (default), return a compact flat array of [id, title, type, depth, wordCount, hasChildren] tuples. When false, return the nested tree object.
folderIdNoUUID of a binder folder, as returned by get_structure.
maxDepthNoMaximum depth to descend into the binder tree, starting at 0 for top-level items. Omit to return the full hierarchy.
summaryOnlyNoWhen true, skip the tree and return only project-level counts (documents, words) plus title and author. Default false.
includeTrashNoSet true to include trashed items in the result. Default false.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
summaryNoProject-level counts plus title and author (present when summaryOnly).
documentsNoFlat list of binder items in tree order (present unless summaryOnly).
structureNoNested binder tree (present when flat is false).
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds value: explains default flat format to save tokens, summaryOnly option, and requirement of open project. No contradiction.

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?

Four sentences, well-structured with purpose first. Every sentence adds value, no redundancy. Concise yet comprehensive.

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 (not shown), description covers return formats, parameters, prerequisites, and usage context. Fully adequate for a read-only tree 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?

Schema coverage is 100%, baseline 3. Description adds context: explains default flat format, that summaryOnly skips the tree, and that folderId comes from prior get_structure calls. Adds meaning beyond schema.

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?

Clearly states it returns binder hierarchy with specific fields (id, title, type, depth, word count). Distinguishes from siblings by noting it provides document IDs required by other tools like read_document and write_document.

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

Usage Guidelines4/5

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

Explicitly says to use for understanding manuscript layout and obtaining document IDs. Also states prerequisite: requires open project. Lacks explicit when not to use alternatives, but context is clear.

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/writerslogic/scrivener-mcp'

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