Skip to main content
Glama
Sign In
SheetForge MCP

SheetForge MCP

by iHeldan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

find_free_canvas

Read-only

Suggests free worksheet slots for charts or dashboard blocks, so you can place visuals without overwriting existing content.

Instructions

Suggest free worksheet slots for charts or dashboard blocks.

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": {
      "filepath": "<filepath>",
      "sheet_name": "<sheet_name>"
    },
    "name": "find_free_canvas"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
widthNo
heightNo
filepathYesReuse supplied server path; NEVER prepend client cwd. Rooted: relative OK; unrooted stdio: absolute, ask if missing.
min_colsNo
min_rowsNo
sheet_nameYes
origin_cellNoA1
search_rowsNo
padding_rowsNo
search_columnsNo
padding_columnsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.14.0
    • addedInput schema / properties / filepath / description
      Added value: +"Reuse supplied server path; NEVER prepend client cwd. Rooted: relative OK; unrooted stdio: absolute, ask if missing."
  2. First observedv0.8.0

TDQS

C2.4/5.0
Behavior2/5

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

readOnlyHint=true already tells the agent this is a safe read, and 'Suggest' is consistent with that. Beyond the annotation the description adds nothing: it does not define what counts as 'free' (empty cells, merged regions, padded gaps) or how candidates are ranked, which is the core behavioral question for this tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero filler, so nothing is wasted. But at 12 parameters and 8% schema coverage, this level of brevity is under-specification rather than effective concision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter tool with almost no schema descriptions and no output schema, the description should explain search semantics, sizing constraints, and what a returned 'slot' looks like. It covers none of that, leaving an agent unable to invoke it correctly without guessing.

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

Parameters1/5

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

Schema description coverage is only 8% (only filepath is documented), and the description explains none of the 12 parameters. The meaning of width/height vs min_cols/min_rows, origin_cell, search_rows/search_columns, and padding_rows/padding_columns is left entirely to bare property names.

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?

States a specific verb and resource ('Suggest free worksheet slots') plus the intended use case ('charts or dashboard blocks'), so the agent knows what it returns. It does not differentiate itself from the closest sibling, describe_sheet_layout, which likely overlaps in layout-awareness.

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

Usage Guidelines2/5

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

The use case implies when it is useful (before placing a chart or dashboard block), but there is no explicit when-to-use/when-not guidance, no prerequisites (workbook open, sheet exists), and no mention of alternatives such as describe_sheet_layout.

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