Skip to main content
Glama

Bilig WorkPaper

by io.github.proompteng

Read WorkPaper Cell

read_cell
Read-onlyIdempotent

Read one cell with calculated value, display text, formula text, formula diagnostics, and serialized content. Use after set_cell_contents to verify readback.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addressYesSingle A1 cell address such as B3.
sheetNameYesExisting sheet name.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueYesCalculated cell value.
addressYesCanonical sheet-qualified A1 address.
formulaYesFormula text without losing the original calculated value context, or null for literal cells.
serializedYesRaw serialized cell content; formulas are strings that start with =.
displayValueYesFormatted value as a user would see it.
formulaDiagnosticsYesStructured formula diagnostics. Empty when the cell has no formula error.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / formulaDiagnostics
      Added value: +{
+  "description": "Structured formula diagnostics. Empty when the cell has no formula error.",
+  "type": "array"
+}
    • changedOutput schema / required
      Previous value: -[
-  "address",
-  "value",
-  "serialized",
-  "formula",
-  "displayValue"
-]New value: +[
+  "address",
+  "value",
+  "serialized",
+  "formula",
+  "displayValue",
+  "formulaDiagnostics"
+]
  2. Changed4 schema fields changed
    • addedOutput schema / properties / formula / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / formula / type
      Removed value: -[
-  "string",
-  "null"
-]
    • addedOutput schema / properties / serialized / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "number"
+  },
+  {
+    "type": "boolean"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / serialized / type
      Removed value: -[
-  "string",
-  "number",
-  "boolean",
-  "null"
-]
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds value by specifying the exact fields returned (calculated value, display text, formula text, etc.), which is useful behavioral context beyond the annotations.

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?

The description is concise with two sentences: the first states the core function and outputs, the second provides a practical usage tip. No unnecessary words or redundancy.

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?

The tool is straightforward (single cell read) with an output schema present. The description covers the key return content and a common use case. It lacks information on error conditions or edge cases, but these are likely captured in the output schema, so completeness is sufficient.

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 coverage is 100% with both parameters (sheetName, address) having descriptions. The description does not add additional parameter semantics beyond the schema, so baseline score of 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?

The description clearly states the tool reads a single cell and lists specific outputs (calculated value, display text, formula text, formula diagnostics, serialized content). It distinguishes from siblings like read_range (one cell vs. range) and get_cell_display_value (more than just display value).

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?

The description explicitly recommends using this tool after set_cell_contents to verify readback, providing a clear usage context. It does not explicitly mention alternatives or exclusions, but the use case is well-defined given the sibling tool names.

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

All Bilig WorkPaper toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation4/5

Tools are mostly distinct with clear purposes for reading, writing, exporting, and validating. Slight overlap exists between get_cell_display_value and read_cell, and between the two set_cell variants, but descriptions clarify the intended use.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (e.g., list_sheets, read_cell, validate_formula). This predictable naming makes the set easy to navigate.

Tool Count5/5

With 8 tools, the set is well-scoped for interacting with a WorkPaper document. Each tool serves a clear purpose without unnecessary bloat.

Completeness3/5

Core operations for reading, writing, validating, and exporting are covered, but the surface lacks batch cell writes, cell clearing, and sheet management. These notable gaps may hinder complex editing workflows.

Resources