Skip to main content
Glama
Sign In
basis1: Excel engine for AI agents (formulas, recalculation, audit)

basis1: Excel engine for AI agents (formulas, recalculation, audit)

Official
by basis1tech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Save to Library

save_to_library

Save the current session workbook to the user's Library as a durable named version, creating a new file or updating an existing one for later reopening and version history.

Instructions

Save the session's workbook to the user's Library for durable storage. If the session was loaded from the Library or was previously saved, this creates a new version of that file. Otherwise it creates a new Library file. Each save is a named version in the Library's history: pass message, or it takes the latest commit_session message since the last save. commit_session checkpoints themselves stay in the session, so save after each step you want kept as a version. Returns {library_file_id, version_id, name, message, created, noop}; noop is true when nothing changed since the last version. Open the file again later with create_session's library_file_id; list_library_files finds it.

Input Schema

NameRequiredDescriptionDefault
nameNoFile name for a new Library file (defaults to the session's document label); not used when saving a new version
messageNoName for this version in the Library, e.g. "23 — revised exit cap" (defaults to the latest commit_session message)
session_idYesSession ID returned by create_session (list_sessions shows the open ones)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.2
    • changedInput schema / properties / name / description
      Previous value: -"File name (defaults to the session's document label)"New value: +"File name for a new Library file (defaults to the session's document label); not used when saving a new version"
    • changedInput schema / properties / session_id / description
      Previous value: -"Session ID"New value: +"Session ID returned by create_session (list_sessions shows the open ones)"
  2. First observedv0.3.1

TDQS

A4.7/5.0
Behavior4/5

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

Beyond the annotations, it discloses the versioning model, the message-inheritance default, and the noop-when-nothing-changed outcome, which is close to idempotency behavior the annotations only hint at with idempotentHint=false. It does not explicitly cover permissions or whether versions can be deleted, so it falls just short of fully carrying the behavioral burden.

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?

Front-loaded with the core action, then the branching rule, then the versioning semantic, then the return shape, then the follow-up pointers. Dense but every sentence carries distinct information an agent needs, with no filler.

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?

There is no output schema, and the description compensates by enumerating the returned fields and explaining the meaning of noop. Combined with the 100%-covered input schema and the annotation set, nothing essential to calling this tool correctly is missing.

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 baseline is 3, but the description adds workflow meaning the schema does not: that name applies only when creating a new file, and that message becomes the named version with a fallback to the latest commit_session message "since the last save". That contextualizes the parameter inside the save/version sequence rather than just restating types.

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?

A specific verb and resource ("Save the session's workbook to the user's Library") plus the branching behavior: new version of an existing file vs. a brand-new Library file. It is clearly distinct from the sibling commit_session, which the description explicitly says keeps checkpoints in the session only.

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

Usage Guidelines5/5

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

It gives explicit when-to-use guidance ("save after each step you want kept as a version"), and draws the boundary against the nearest alternative by explaining that commit_session checkpoints stay in the session. It also names the follow-up path: reopen via create_session's library_file_id, discover via list_library_files.

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

Deploy Server

Other Tools