Skip to main content
Glama
Sign In
WiseGrid MCP

WiseGrid MCP

by RyanKramer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_sheet

Retrieve a sheet's columns and first page of rows in one call to get a usable snapshot before writing data. Identify column IDs.

Instructions

Get a sheet with its columns and first page of rows — one call for a usable snapshot. Use this before writing, to learn the column IDs.

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": {
      "sheet_id": "<sheet_id>"
    },
    "name": "get_sheet"
  }
}

Input Schema

NameRequiredDescriptionDefault
sheet_idYes
row_limitNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the burden of disclosure. It does reveal key behavior: returns columns and rows, and is a snapshot. However, it does not explain row_limit behavior, error cases, or authentication needs, leaving some gaps.

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?

Two sentences, front-loaded with the key point, and every sentence adds value. No filler 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?

Given the existence of an output schema and the tool's simplicity, the description covers the essential purpose, return contents, and usage hint. The only notable omission is explicit row_limit semantics, but the overall context is sufficient for an agent to use it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description only hints at row_limit via 'first page' and sheet_id via 'to learn the column IDs'. It does not explicitly define either parameter's meaning or how row_limit affects the result, so it fails to compensate for the lack of schema descriptions.

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 retrieves a sheet with columns and the first page of rows, which distinguishes it from siblings like list_sheets, list_columns, and list_rows. The phrase 'one call for a usable snapshot' reinforces the combined functionality.

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?

Explicit guidance is provided: 'Use this before writing, to learn the column IDs.' This tells the agent when to invoke the tool, but it does not explicitly mention when not to use alternatives or name them, so it falls short of a full 5.

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