Skip to main content
Glama
Sign In
SheetForge MCP

SheetForge MCP

by iHeldan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

detect_circular_dependencies

Read-only

Detect circular formula dependencies in Excel workbooks, including self-references, to identify and fix broken calculation chains.

Instructions

Detect circular workbook formula dependencies, including self-references.

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>"
    },
    "name": "detect_circular_dependencies"
  }
}

Input Schema

NameRequiredDescriptionDefault
filepathYesReuse supplied server path; NEVER prepend client cwd. Rooted: relative OK; unrooted stdio: absolute, ask if missing.
sample_limitNo

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.9/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe non-mutating operation, so the description need not re-establish that. It adds the useful scope detail that self-references count as circular, but says nothing about whether the scan covers the whole workbook or a single sheet, how results are reported, or cost on large files.

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

Conciseness4/5

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

A single front-loaded sentence with no filler and the key scope qualifier placed immediately. Its brevity is close to under-specification rather than elegance, but nothing is wasted.

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

Completeness2/5

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

With no output schema, the description carries the burden of explaining the return shape (list of cycles? paths? cells?) and it does not. Combined with an undocumented sample_limit and no statement of scan scope, an agent cannot fully predict what a call yields.

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 coverage is only 50%: filepath is well documented in the schema, but sample_limit has no description anywhere. The tool description says nothing about what sample_limit controls or that its default of 25 bounds the reported cycles, leaving a real gap the description should have closed.

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?

Specific verb (detect) plus resource (circular workbook formula dependencies) and an explicit scope extension (including self-references). It does not, however, distinguish itself from nearby diagnostic siblings such as validate_formula_syntax, inspect_formula, or audit_workbook, which an agent could plausibly reach for instead.

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 description gives no when-to-use context, no prerequisites, and no routing to alternatives. It never says whether this is the right tool for a full audit versus a single-formula check, even though validate_formula_syntax and audit_workbook are available siblings.

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