Skip to main content
Glama
SoManyLemons MCP

SoManyLemons MCP

Official
by NoMiddleInc

Read task spreadsheet

read_task_spreadsheet
Read-onlyIdempotent

Reads a research task's saved spreadsheet in one call, returning all sheets or a chosen sheet with headers, row counts, and rows; reports truncation and is read-only.

Instructions

The complete saved spreadsheet of a research task in one call: every sheet, or one sheet_name. include_rows=false returns only sheets_summary (sheet names, headers and row counts). The result says when rows were truncated. Reads only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "goal_id": "<goal_id>",
      "artifact_id": "<artifact_id>"
    },
    "name": "read_task_spreadsheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
goal_idYes
sheet_nameNo
artifact_idYes
include_rowsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.36

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, and non-destructive behavior, so the description adds useful context beyond them: it describes the summary-only mode and that truncated rows are reported. It does not cover authentication or broader result shape, but it is transparent about the key read behavior.

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 short, front-loaded, and every sentence contributes: scope, sheet selection, summary mode, truncation, and read-only confirmation. 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 four-parameter read tool with no output schema, the description gives enough behavioral context to call it correctly in common cases, including summary mode and truncation reporting. It is incomplete only around the required ID parameters and lacks explicit alternative-tool guidance.

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 0%, so the description must carry parameter meaning. It clearly explains sheet_name and include_rows, but it does not explain the required goal_id and artifact_id parameters, leaving half the parameters without added semantics.

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 states a specific verb and resource: read the complete saved spreadsheet of a research task. It makes the scope clear by saying every sheet or one sheet_name, but it does not explicitly distinguish this from sibling artifact/task read tools.

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?

It implies when to use the tool and explains one useful mode: include_rows=false returns only a sheets_summary. However, it gives no explicit when-not conditions or named alternatives for reading other task artifacts.

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