Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_monday_boards

Read-onlyIdempotent

Retrieve boards from a Monday.com account to inspect available workspaces, with an optional limit and API key authentication.

Instructions

List boards in a Monday.com account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_monday_boards"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax boards to return (default 25)
api_keyNoMonday.com API token (or set MONDAY_API_KEY)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.9
  2. Removed
  3. Addedv0.1.5

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false. The description adds only account-level scoping; it does not describe pagination behavior, auth requirements beyond the schema, or return shape.

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?

It is a single front-loaded sentence with no filler. For a simple listing tool, the brevity is efficient.

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

Completeness3/5

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

The tool is simple and read-only, annotations cover safety, and the schema covers both parameters. However, the description leaves gaps around pagination behavior and what board data is returned, which matters more because there is no output schema.

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 description coverage is 100%, with limit documented as default 25 and api_key documented with MONDAY_API_KEY fallback. The description adds no parameter meaning beyond the schema, so the baseline 3 applies.

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?

The description uses a specific verb and resource: 'List boards' in a Monday.com account. It is distinguishable from get_monday_board, but it does not explicitly name that sibling or clarify the board-level vs account-level distinction beyond the word 'List'.

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?

There is no when-to-use or when-not-to-use guidance, no mention of alternatives such as get_monday_board or list_monday_items, and no prerequisites. The agent must infer usage from the name and one-line description.

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