Skip to main content
Glama

hedwigai

Start a new workbook

create_workbook

Makes a new workbook from EXACTLY ONE of: instruction — one sentence the way a person would say it ('find 30 US importers of loose leaf tea and the buyer at each'), which starts a run that researches and writes it, is billed to this account and takes minutes; document — markdown you have written, which becomes version 1 at once; or sheets — tabs, each {name, markdown}, which become version 1 at once. Writing content yourself runs nothing and costs nothing. Nothing that already exists is changed.

Input Schema

NameRequiredDescriptionDefault
modeNoWhat this workbook's runs are, from now on. `harnessroom` (a new workbook's default): the instruction is a request, and a harness researches and writes the document. `latticeroom`: the instruction is a draft someone already wrote, whole — markdown, its links kept — which comes back exactly as written, with the run's inference beside it (read_workbook's `inference`: each claim cited, self-reported, secondary only, contradicted or with no source, and its sources); each entry under its References or Bibliography heading is looked up in Crossref and on the web and marked found, found with other authors or year, or not found, and a sentence citing it — [3], (Smith et al., 2020) — is read against the work found; attach data files (.json, .csv, .tsv) to settle the draft's own figures. `graphroom`: runs perform the procedure drawn for the workbook in the app, and refuse until one is drawn. `flashroom`, for a workbook made from a spreadsheet or a Word document: the instruction is an edit to its sheet, or to the document's table it is about, planned in seconds and kept in `messages` — each cell's before and after, the rows added and removed — and nothing is written until the next instruction is `yes`, which makes it as a new version. Omit to keep the workbook's current mode.
nameNoIts name. A name another workbook has is told apart by this one's id.
workNotrue when the instruction is work to do and never a question — your own router already said so. The run starts without first being asked whether it is a question.
modelNoThe model its runs think with, as configure_workbook names them — set before the first run.
titleNoWhat it is shown by, e.g. 'Comps', where the name has to say more. Need not be unique: the name stays its address.
folderNoA folder to put it in, e.g. 'Outreach'. Made if missing. Omit for the root.
sheetsNoThe first version as tabs, in order.
contextNoExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
documentNoThe first version as markdown, written by you.
llm_modelNoThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
attachmentsNoFiles to attach to the workbook BEFORE the run starts, so it reads and cites them — each {name, content_base64, content_type?}, 32 MB at most. They stay attached for every later run; list_attachments shows them.
instructionNoWhat the workbook should be, in one sentence. A billed run writes it.
sources_folderNoThe drive folder you keep this workbook's subject in — `/dropbox/Trevi Therapeutics`. What the run cites is filed there once it delivers, instead of a folder named after the document's title.
time_limit_secondsNoHow long its first run may take, for a run a person waits on: stopped there, it delivers the draft it has. Set before the run starts, so one call makes and starts it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / mode / description
      Previous value: -"What this workbook's runs are, from now on. `harnessroom` (a new workbook's default): the instruction is a request, and a harness researches and writes the document. `latticeroom`: the instruction is a draft someone already wrote, whole — markdown, its links kept — which comes back exactly as written, with the run's inference beside it (read_workbook's `inference`: each claim cited, self-reported, secondary only, contradicted or with no source, and its sources); each entry under its References or Bibliography heading is looked up in Crossref and on the web and marked found, found with other authors or year, or not found, and a sentence citing it — [3], (Smith et al., 2020) — is read against the work found; attach data files (.json, .csv, .tsv) to settle the draft's own figures. `graphroom`: runs perform the procedure drawn for the workbook in the app, and refuse until one is drawn. Omit to keep the workbook's current mode."New value: +"What this workbook's runs are, from now on. `harnessroom` (a new workbook's default): the instruction is a request, and a harness researches and writes the document. `latticeroom`: the instruction is a draft someone already wrote, whole — markdown, its links kept — which comes back exactly as written, with the run's inference beside it (read_workbook's `inference`: each claim cited, self-reported, secondary only, contradicted or with no source, and its sources); each entry under its References or Bibliography heading is looked up in Crossref and on the web and marked found, found with other authors or year, or not found, and a sentence citing it — [3], (Smith et al., 2020) — is read against the work found; attach data files (.json, .csv, .tsv) to settle the draft's own figures. `graphroom`: runs perform the procedure drawn for the workbook in the app, and refuse until one is drawn. `flashroom`, for a workbook made from a spreadsheet or a Word document: the instruction is an edit to its sheet, or to the document's table it is about, planned in seconds and kept in `messages` — each cell's before and after, the rows added and removed — and nothing is written until the next instruction is `yes`, which makes it as a new version. Omit to keep the workbook's current mode."
    • changedInput schema / properties / mode / enum
      Previous value: -[
      -  "harnessroom",
      -  "latticeroom",
      -  "graphroom"
      -]New value: +[
      +  "harnessroom",
      +  "latticeroom",
      +  "graphroom",
      +  "flashroom"
      +]
    • addedInput schema / properties / title
      Added value: +{
      +  "description": "What it is shown by, e.g. 'Comps', where the name has to say more. Need not be unique: the name stays its address.",
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedInput schema / properties / sources_folder
      Added value: +{
      +  "description": "The drive folder you keep this workbook's subject in — `/dropbox/Trevi Therapeutics`. What the run cites is filed there once it delivers, instead of a folder named after the document's title.",
      +  "type": "string"
      +}
    • addedInput schema / properties / work
      Added value: +{
      +  "description": "true when the instruction is work to do and never a question — your own router already said so. The run starts without first being asked whether it is a question.",
      +  "type": "boolean"
      +}
  3. Changed2 schema fields changed
    • removedInput schema / properties / economy
      Removed value: -{
      -  "description": "How its harnessroom runs keep their transcript small; compaction is the default.",
      -  "enum": [
      -    "compaction",
      -    "steering",
      -    "delegation",
      -    "unbounded"
      -  ],
      -  "type": "string"
      -}
    • removedInput schema / properties / preload_methods
      Removed value: -{
      -  "description": "Whether the methods the instruction names are put into its first run before it starts. On by default.",
      -  "type": "boolean"
      -}
  4. Changed2 schema fields changed
    • addedInput schema / properties / economy
      Added value: +{
      +  "description": "How its harnessroom runs keep their transcript small; compaction is the default.",
      +  "enum": [
      +    "compaction",
      +    "steering",
      +    "delegation",
      +    "unbounded"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / preload_methods
      Added value: +{
      +  "description": "Whether the methods the instruction names are put into its first run before it starts. On by default.",
      +  "type": "boolean"
      +}
  5. Changed3 schema fields changed
    • addedInput schema / properties / model
      Added value: +{
      +  "description": "The model its runs think with, as configure_workbook names them — set before the first run.",
      +  "type": "string"
      +}
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "Its name. A name another workbook has is told apart by this one's id.",
      +  "type": "string"
      +}
    • addedInput schema / properties / time_limit_seconds
      Added value: +{
      +  "description": "How long its first run may take, for a run a person waits on: stopped there, it delivers the draft it has. Set before the run starts, so one call makes and starts it.",
      +  "maximum": 14400,
      +  "minimum": 20,
      +  "type": "integer"
      +}
  6. Changed1 schema field changed
    • changedInput schema / properties / mode / description
      Previous value: -"What this workbook's runs are, from now on. `harnessroom` (a new workbook's default): the instruction is a request, and a harness researches and writes the document. `latticeroom`: the instruction is a draft someone already wrote, whole — markdown, its links kept — which comes back exactly as written, with the run's inference beside it (read_workbook's `inference`: each claim cited, self-reported, secondary only, contradicted or with no source, and its sources); attach data files (.json, .csv, .tsv) to settle the draft's own figures. `graphroom`: runs perform the procedure drawn for the workbook in the app, and refuse until one is drawn. Omit to keep the workbook's current mode."New value: +"What this workbook's runs are, from now on. `harnessroom` (a new workbook's default): the instruction is a request, and a harness researches and writes the document. `latticeroom`: the instruction is a draft someone already wrote, whole — markdown, its links kept — which comes back exactly as written, with the run's inference beside it (read_workbook's `inference`: each claim cited, self-reported, secondary only, contradicted or with no source, and its sources); each entry under its References or Bibliography heading is looked up in Crossref and on the web and marked found, found with other authors or year, or not found, and a sentence citing it — [3], (Smith et al., 2020) — is read against the work found; attach data files (.json, .csv, .tsv) to settle the draft's own figures. `graphroom`: runs perform the procedure drawn for the workbook in the app, and refuse until one is drawn. Omit to keep the workbook's current mode."
  7. Changed2 schema fields changed
    • changedInput schema / properties / mode / description
      Previous value: -"What this workbook's runs do, from now on. `research` (a new workbook's default): the instruction is a request, and the run finds sources and writes the document. `ground`: the instruction is a draft someone already wrote, whole — markdown, its links kept — and the run leaves every word as written and marks each claim cited (with the passage quoted), self-reported, secondary only, contradicted or with no source. Link data files on the account's drive (/dropbox/...json, .csv) in the draft to settle its own figures. Omit to keep the workbook's current mode."New value: +"What this workbook's runs are, from now on. `harnessroom` (a new workbook's default): the instruction is a request, and a harness researches and writes the document. `latticeroom`: the instruction is a draft someone already wrote, whole — markdown, its links kept — which comes back exactly as written, with the run's inference beside it (read_workbook's `inference`: each claim cited, self-reported, secondary only, contradicted or with no source, and its sources); attach data files (.json, .csv, .tsv) to settle the draft's own figures. `graphroom`: runs perform the procedure drawn for the workbook in the app, and refuse until one is drawn. Omit to keep the workbook's current mode."
    • changedInput schema / properties / mode / enum
      Previous value: -[
      -  "research",
      -  "ground"
      -]New value: +[
      +  "harnessroom",
      +  "latticeroom",
      +  "graphroom"
      +]
  8. Changed1 schema field changed
    • addedInput schema / properties / mode
      Added value: +{
      +  "description": "What this workbook's runs do, from now on. `research` (a new workbook's default): the instruction is a request, and the run finds sources and writes the document. `ground`: the instruction is a draft someone already wrote, whole — markdown, its links kept — and the run leaves every word as written and marks each claim cited (with the passage quoted), self-reported, secondary only, contradicted or with no source. Link data files on the account's drive (/dropbox/...json, .csv) in the draft to settle its own figures. Omit to keep the workbook's current mode.",
      +  "enum": [
      +    "research",
      +    "ground"
      +  ],
      +  "type": "string"
      +}
  9. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
      +  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
      +  "type": "string"
      +}
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
      +  "type": "string"
      +}
  10. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only declare the safety profile (readOnlyHint=false, destructiveHint=false, non-idempotent, open-world); the description adds genuinely new behavior: instruction mode is a billed run taking minutes, self-authored content costs nothing and starts nothing, and 'Nothing that already exists is changed.' It also flags that attachments persist across every later run, which is not derivable from the schema.

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?

The core constraint is front-loaded in the first clause and every sentence carries information (mode semantics, billing, permanence of attachments). Sentences are long and clause-heavy, and the trailing 'Nothing that already exists is changed' is doing safety work that could be stated more plainly, but there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 14-parameter creation tool with no output schema, the description covers the creation paths, cost model, and non-destructiveness well. It omits what the call returns (presumably a workbook id used by read_workbook/configure_workbook), which an agent needs to chain follow-up calls, and leaves the mode enum entirely to the schema.

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%, so the schema already documents each field; the description's added value is the mutual-exclusivity constraint across instruction/document/sheets, which the schema cannot express (no required fields, no oneOf). It adds little on the remaining 11 params such as name, folder, time_limit_seconds, or the analytics fields, but those are fully covered in-schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Makes a new workbook') and immediately narrows the input to exactly one of three named shapes, so the agent knows what it is creating and from what. It never names the sibling it contrasts with (update_workbook / write_workbook); the differentiation is only implied by 'new' and 'Nothing that already exists is changed'.

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?

Gives clear selection rules among the three input modes, including the cost/latency consequence that separates them: instruction 'starts a run ... is billed to this account and takes minutes' versus 'Writing content yourself runs nothing and costs nothing.' It does not say when to reach for this tool at all versus write_workbook or update_workbook on an existing workbook.

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.