Skip to main content
Glama

hedwigai

See or change a workbook's settings

configure_workbook
DestructiveIdempotent

A workbook's settings, and changes to them: its name; its title — what it is shown by, where that is shorter than its name; its mode — harnessroom, latticeroom, graphroom or flashroom (a harnessroom researches and writes; a latticeroom is handed a draft and marks each claim with its sources, and each reference with whether the work exists, leaving the words as written; a graphroom performs the procedure drawn for it in the app; a flashroom plans an edit to its spreadsheet and makes it on yes); for a harnessroom, the model its runs think with (one of the nodes this answers with), the harness that drives it, the time a run gets — time_limit_minutes, or time_limit_seconds for a run someone waits on — and its economy; the members it belongs to; and the storage its runs file sources into. Send only what should change — the rest stays. With nothing to change it only reads. Changes apply from the next run.

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.
nameNoA new name for the workbook.
modelNoThe model a harnessroom's runs think with: a `node` from this tool's answer.
titleNoWhat it is shown by, over its name. Need not be unique. An empty string clears it.
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."
economyNoHow a harnessroom run keeps its transcript small: compaction (the default), steering, delegation, or unbounded.
harnessNoThe coding harness that drives a harnessroom run.
membersNoEvery member's email, the whole list: who the workbook is shared with and who its email goes to.
storageNoWhere runs file the sources they save: a connected drive, or auto (the first connected).
workbookYesThe workbook id.
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.
time_limit_minutesNoHow long a harnessroom run may take before it is stopped.
time_limit_secondsNoThe same in seconds, for a run a person waits on: stopped there, it delivers the draft it has written. Give this or time_limit_minutes, not both.

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, over its name. Need not be unique. An empty string clears it.",
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • removedInput schema / properties / preload_methods
      Removed value: -{
      -  "description": "Whether the methods the instruction names are put into a harnessroom run before it starts. On by default; false is for measuring what that does.",
      -  "type": "boolean"
      -}
  3. Changed1 schema field changed
    • addedInput schema / properties / preload_methods
      Added value: +{
      +  "description": "Whether the methods the instruction names are put into a harnessroom run before it starts. On by default; false is for measuring what that does.",
      +  "type": "boolean"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / time_limit_seconds
      Added value: +{
      +  "description": "The same in seconds, for a run a person waits on: stopped there, it delivers the draft it has written. Give this or time_limit_minutes, not both.",
      +  "maximum": 14400,
      +  "minimum": 20,
      +  "type": "integer"
      +}
  5. 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."
  6. Changed6 schema fields changed
    • changedInput schema / properties / economy / description
      Previous value: -"How a research run keeps its transcript small: compaction (the default), steering, delegation, or unbounded."New value: +"How a harnessroom run keeps its transcript small: compaction (the default), steering, delegation, or unbounded."
    • changedInput schema / properties / harness / description
      Previous value: -"The coding harness that drives a research run."New value: +"The coding harness that drives a harnessroom run."
    • 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"
      +]
    • changedInput schema / properties / model / description
      Previous value: -"The model research runs think with: a `node` from this tool's answer."New value: +"The model a harnessroom's runs think with: a `node` from this tool's answer."
    • changedInput schema / properties / time_limit_minutes / description
      Previous value: -"How long a research run may take before it is stopped."New value: +"How long a harnessroom run may take before it is stopped."
  7. Added

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations, it discloses patch-style preservation of omitted settings, conditional read-only behavior, deferred effects, and significant mode behavior such as latticeroom preserving draft wording and flashroom waiting for `yes`. It does not explain what makes the operation destructive or describe the complete read response, so it is informative rather than exhaustive.

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

Conciseness3/5

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

The material is logically grouped and contains little irrelevant prose, but the opening sentence is excessively long and semicolon-heavy, repeating enum values and mode details already present in the schema. The most operational rules—partial updates, empty-call reads, and next-run effects—are useful but buried at the end instead of being front-loaded.

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 complex 13-parameter tool without an output schema, the description covers the main settings, mode distinctions, update semantics, timing of effects, and one useful response detail about available model nodes. Remaining gaps are sibling-tool routing, the scope of destructive changes, and a fuller account of what a settings read returns.

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?

Although schema description coverage is 100%, the description adds useful cross-parameter meaning: which settings apply only to harnessrooms, how the two time limits differ, that valid models come from the answer's `nodes`, and how omitted fields behave. It adds little about the required workbook identifier or analytics parameters, but those are not central to configuring the workbook.

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?

The description clearly identifies a tool for reading or changing workbook settings and enumerates the configurable name, title, mode, harnessroom run options, members, and storage. Its explanations of the four modes clarify the resource well, but it does not distinguish this tool from siblings such as `update_workbook` or `create_workbook`.

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?

It gives concrete invocation guidance: send only fields that should change, provide no changes to perform a read, and expect changes to apply from the next run. Mode-specific settings further guide selection, but there are no explicit when-not rules or alternatives among the sibling tools.

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.