Skip to main content
Glama

hedwigai

by com.hedwigai
OverviewDiscussionsAdmin

Link a workbook to a file in Drive or Dropbox

link_workbook
Idempotent

Makes a file in this account's Google Drive or Dropbox the document of record for a workbook. The file is brought in now — an empty workbook is seeded from it, and one with versions gets its content as the next version — and from then on:

  • every run and every checkout_workbook brings the file in first, so work starts from what is in the drive, including an edit made in Excel or Word since;

  • every new version is written back over the file IN PLACE (the same Drive file, its sharing and revision history kept).

An Excel workbook (.xlsx, .xlsm) is edited as the spreadsheet itself: a run gets it as draft.xlsx and the xlsx program, and the file goes back with its formulas, formats and every untouched sheet as they were. A Word document (.docx) is edited as markdown and written back into its own package, so its styles, headers and footers stay.

A file changed in the drive while a run was working is NOT overwritten; the workbook's link.last_error says so, and the next pull brings that change in.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesThe file on a mount, as the shell names it: `googledrive/Sites/339 15th St/Rent Builder.xlsx` or `dropbox/memo.docx`.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes far beyond the annotations: it discloses that runs and checkout_workbook pull the file first, that new versions are written back IN PLACE preserving sharing/revision history, format-specific handling for .xlsx/.docx, and the conflict case (a file changed mid-run is not overwritten; link.last_error reports it). Rich behavioral context that annotations alone (idempotent, openWorld) would never convey.

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 purpose, then well-chunked bullets for the run/checkout and write-back behaviors. Length is substantial but the detail earns its place for a stateful linking operation; minor redundancy, but no wasted sentences.

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?

No output schema exists, and the description fully covers what an agent needs: seeding vs versioning on link, ongoing sync behavior, format handling, and the failure/conflict path. Nothing material is omitted for a tool of this complexity.

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 schema already documents path, workbook, context, and llm_model. The description adds little about parameter meaning beyond the format examples already present in the schema. Baseline 3 is appropriate.

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 ('Makes a file ... the document of record for a workbook'), naming the exact scopes (Google Drive / Dropbox). An agent can distinguish this from unlink_workbook or create_workbook without opening any schema.

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?

The description heavily conveys the consequences of linking, which implies when to call it, but never states explicit when-to-use conditions, prerequisites, or the alternative (unlink_workbook). Usage is inferable but not spelled out.

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

All hedwigai toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources