Skip to main content
Glama
crunchtools

MCP WorkBoard CrunchTools

by crunchtools

workboard_create_objective_tool

Create a new objective with optional key results. Specify goal name, owner, start and target dates, and optionally add key results with metric targets.

Instructions

Create a new objective with optional key results (requires Data-Admin token).

Provide the goal name, owner, dates, and optionally key results with targets. Each key result dict can include: metric_name, metric_start, metric_target, metric_type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesObjective name (e.g. "Increase customer retention")
ownerYesOwner's email address or user ID
start_dateYesStart date in YYYY-MM-DD format
target_dateYesTarget completion date in YYYY-MM-DD format
narrativeNoOptional description/narrative for the objective
goal_typeNo"1" for Team objective (default), "2" for Personal objective1
permissionNoVisibility setting (default "internal,team")internal,team
key_resultsNoOptional list of key result dicts, each with keys like "metric_name", "metric_start", "metric_target", "metric_type"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Discloses the auth requirement and optional key results structure. With no annotations, it carries the burden but does not cover error behavior, idempotency, or other constraints.

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 concise sentences with no wasted words. Front-loaded with purpose and auth requirement.

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?

With an output schema present, description covers creation purpose, required parameters, optional key results, and auth. Missing some edge cases but adequate for the tool's complexity.

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 has 100% description coverage, so the description adds limited new meaning. It summarizes required fields and explains key results, but this largely mirrors the schema.

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?

Description clearly states the tool creates an objective with optional key results. It distinguishes itself from sibling tools (e.g., create_activity, create_user) by focusing on objectives.

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?

Mentions the required Data-Admin token, providing a usage prerequisite. Does not explicitly state when not to use or compare with alternatives, but context is clear given sibling names.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/crunchtools/mcp-workboard'

If you have feedback or need assistance with the MCP directory API, please join our Discord server