Skip to main content
Glama

hedwigai

Ask a workbook to change

update_workbook

Starts a run on the workbook, described in one sentence the way a person would say it — 'add a section on Q3 headcount', 'refresh the cash figures from the latest filing'. The run is billed to this account and takes minutes; this returns its run id immediately and does not wait. The workbook shows what changed once the run finishes. An instruction that is a question about the workbook — 'which rows have no source?' — is answered instead, in seconds, from the workbook's own text: no version is written, and read_workbook's messages holds the answer under this run's id.

Input Schema

TableJSON 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. Omit to keep the workbook's current mode.
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."
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.
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.
instructionYesWhat should change, in one sentence — or, for a latticeroom, the whole draft to ground.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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."
  2. Changed3 schema fields changed
    • changedInput schema / properties / instruction / description
      Previous value: -"What should change, in one sentence — or, in `ground` mode, the whole draft to ground."New value: +"What should change, in one sentence — or, for a latticeroom, the whole draft to ground."
    • 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"
      +]
  3. Changed2 schema fields changed
    • changedInput schema / properties / instruction / description
      Previous value: -"What should change, in one sentence."New value: +"What should change, in one sentence — or, in `ground` mode, the whole draft to ground."
    • 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"
      +}
  4. 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"
      +}
  5. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false) and the description layers on facts they don't carry: the run is billed to this account, takes minutes, returns a run id immediately without waiting, and the workbook reflects changes only when the run finishes. It also discloses the second, non-writing behavior for question-shaped instructions. No contradiction with destructiveHint=false.

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 core action, and every sentence carries distinct information (billing, latency, async return, question fallback). It leans toward long run-on clauses and buries the read_workbook cross-reference at the end, 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 6-parameter mutation tool with no output schema, the description supply enough: it says what comes back (a run id) and that it does not block. It stops short of telling the agent how to track completion (list_runs, get_trace, stop_run exist as siblings), which is the main remaining gap.

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 description coverage is 100%, so the baseline is 3, and the mode enum's rich semantics live in the schema rather than the description. The description does add the example instruction shape and reiterates that a latticeroom instruction is a whole draft, but that is marginal value over the 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?

The description names a specific verb and resource — 'Starts a run on the workbook' — and pins the input form ('one sentence the way a person would say it') with concrete examples. It also carves out the question-shaped instruction case and routes the answer to read_workbook's `messages`, which distinguishes it from the read-side sibling.

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 clear usage context and examples ('add a section on Q3 headcount', 'refresh the cash figures'), plus an explicit when-not path for questions. What's missing is any mention of the sibling write paths (write_workbook, commit_workbook) so the agent can tell a direct edit from a run.

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.