Skip to main content
Glama
crunchtools

MCP WorkBoard CrunchTools

by crunchtools

workboard_get_user_key_results_tool

Retrieve key results owned by a WorkBoard user. Provide user ID to see current year metrics; set include_prior_years to true for past years.

Instructions

List key results (metrics) for a specific WorkBoard user by their user ID.

Use this to see KRs owned by or associated with any user — for example, to review a direct report's key results before a 1:1. Skills layer maps organizational roles (e.g. "direct report") to user IDs; this tool only knows about WorkBoard user IDs.

Use workboard_get_teams_tool and workboard_get_team_members_tool to resolve a person's name to their user ID.

By default, only shows current year key results. Set include_prior_years=True to see key results from previous years.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_idYesUser ID (positive integer). Get this from workboard_get_team_members_tool.
include_prior_yearsNoIf True, include key results from prior years. Defaults to False (current year only).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations provided, but description explains default behavior (current year only) and the optional include_prior_years parameter. Does not explicitly state read-only, but tool name and description imply retrieval. No contradictions.

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?

Concise yet informative. Four sentences, each adding value. Front-loaded with purpose, then usage guidance, then parameter context. No wasted words.

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

Completeness5/5

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

Given output schema exists and parameters are fully described in schema and further in description, the tool is complete. It covers scope (any user), default filter, and hints for resolving IDs.

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 100%, so both parameters have descriptions. The description adds value by explaining how to obtain the user_id from other tools and clarifying the default behavior of include_prior_years.

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?

Clearly states it lists key results for a specific user by user ID. Distinguishes from sibling 'workboard_get_my_key_results_tool' by specifying 'any user' and from other tools by focusing on key results.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use (reviewing KRs, e.g., for direct reports) and provides pointers to resolve names to IDs via other tools. Also notes limitation: only knows WorkBoard user IDs, not organizational roles.

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