Atwork

Set Sheet Dependencies

sheet.set_dependencies

DestructiveIdempotent

Turn dependencies on or off for a worksheet or tasksheet. On adds the Blocking / Blocked By fields (or brings them back with their links); off hides them from every view and keeps the links. Once on, link rows with item.update_humanized / item.create_humanized using Blocked By (or Blocking) values given as item titles, Index (#10) or ids from the same sheet. Off is refused while the sheet has a Gantt view.

Input Schema

Name	Required	Description	Default
`enabled`	Yes	true adds the Blocking / Blocked By fields; false hides them and keeps the links
`sheetId`	Yes

Output Schema

Name	Required	Description
`enabled`	Yes	Whether the sheet now has dependencies
`blockingAttributeId`	Yes	Id of the Blocking field; null when off
`blockedByAttributeId`	Yes	Id of the Blocked By field; null when off

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 4, 2026
- removedOutput schema / properties / blockedByAttributeId / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / blockedByAttributeId / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / blockingAttributeId / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / blockingAttributeId / type
```
Added value: +[
+  "number",
+  "null"
+]
```
First observedOct 20, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing state persistence ('off hides them from every view and keeps the links'), the restore behavior of turning it back on, and a precondition that rejects the operation (Gantt view present). These are exactly the mutation and failure-mode details an agent needs beyond destructiveHint/idempotentHint.

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?

Four sentences, front-loaded with purpose and state semantics, followed by the follow-up workflow and the refusal condition. No filler, though the linking sentence is dense enough to need a second read.

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?

An output schema exists so return values need no explanation, and the description covers the mutation outcome, the persistence rule, and the blocked case. Remaining gaps are minor: it doesn't say which sheet types are valid for sheetId or what permissions are required.

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 50%: 'enabled' is documented in the schema and the description largely restates it, while 'sheetId' is undocumented in both places. The added detail about item titles, '#10' indexes and ids relates to the follow-up linking tools rather than this tool's own parameters.

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?

Opens with a specific verb and resource ('Turn dependencies on or off for a worksheet or tasksheet'), which is clearly distinct from siblings like sheet.update or sheet.add_attribute. It does not explicitly name a competing sibling, but the scope is unambiguous on its own.

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?

Explains the on and off cases and points to the tools to use afterward (item.update_humanized / item.create_humanized) for creating links, plus a hard exclusion ('Off is refused while the sheet has a Gantt view'). No guidance on when to prefer this over, say, reconfiguring a view, but the operating context is clear.

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

All Atwork tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?