Skip to main content
Glama

Connect monday.com and synchronize lists

spur_manage_monday_sync
Destructive

Get a secure OAuth handoff link, disconnect, enable list-to-board sync, run sync now, or disable it. Sync writes prospect data to monday.com; approve the exact list/board first. No tokens or credentials are accepted in chat.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description adds genuine context beyond them: that sync writes prospect data into an external system and that approval must cover the exact list/board. It stops short of disclosing what disconnect or disable actually removes, which matters for the destructive actions.

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, action inventory front-loaded, then the two safety constraints. No filler or restated boilerplate.

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 multi-action, no-output-schema tool this covers every action plus the security and approval model. The gap is the lack of any statement about post-disconnect/disable state or what connect returns besides a link.

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

Parameters4/5

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

Schema coverage is reported high and the confirm field is self-documented, so the baseline is 3; the description earns an extra point by explaining the list_id/board_id relationship (list-to-board sync) and by tying both IDs to an explicit user-approval requirement. It does not explain what happens when board_id is omitted.

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 names all five concrete operations (get OAuth handoff link, disconnect, enable list-to-board sync, run sync now, disable) with specific verbs and resources, mapping cleanly onto the oneOf action constants. An agent can tell exactly what capability this tool exposes without opening the schema.

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?

It supplies two real selection guardrails: approve the exact list/board before syncing, and never accept tokens or credentials in chat. It does not, however, say when to prefer this over a sibling or what to do if no connection exists yet, so guidance is clear but incomplete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources