Skip to main content
Glama
crunchtools

MCP WorkBoard CrunchTools

by crunchtools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Workboard Get My Objectives Tool

workboard_get_my_objectives_tool
Read-only

Retrieve your current objectives and key results without IDs. Auto-discovers OKRs from your key results for a quick view of personal goals.

Instructions

Get the current authenticated user's objectives with key results.

This is the RECOMMENDED tool when users ask about "my objectives" or "my OKRs". It automatically determines the current user and discovers their objectives from their key results — no IDs needed.

Input Schema

NameRequiredDescriptionDefault
objective_idsNoOptional list of specific objective IDs to fetch (at most 25). If not provided, objectives are auto-discovered from the user's key results.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.0
    • changedInput schema / properties / objective_ids / anyOf
      Previous value: -[
-  {
-    "items": {
-      "type": "integer"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "minimum": 1,
+      "type": "integer"
+    },
+    "maxItems": 25,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / objective_ids / description
      Previous value: -"Optional list of specific objective IDs to fetch.\n           If not provided, objectives are auto-discovered from\n           the user's key results."New value: +"Optional list of specific objective IDs to fetch (at most 25).\n           If not provided, objectives are auto-discovered from\n           the user's key results."
  2. Addedv0.7.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so safety is covered, and the description adds genuinely new behavior: it auto-resolves the current user and discovers objectives through their key results rather than requiring IDs. It does not mention rate limits or result-set size, but with annotations and an output schema present the remaining burden is small.

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?

Three tight sentences with the resource and the recommendation front-loaded; every sentence earns its place and there is no restating of the title or schema.

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?

With readOnlyHint annotations, a fully described single parameter, and an output schema covering return values, nothing an agent needs to call this correctly is missing. The auto-discovery behavior — the one thing not expressible in schema — is stated.

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% and the single optional parameter is fully documented there, so the schema does the heavy lifting. The description reinforces the no-ID default and the key-result discovery path, which adds a little meaning but no syntax or format detail beyond the schema — baseline 3.

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?

States a specific verb and resource (get the current authenticated user's objectives with key results) and explicitly scopes it to the current user, which separates it from workboard_get_objectives_tool and workboard_get_user_key_results_tool. An agent can select it 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?

Gives a clear triggering condition — 'when users ask about "my objectives" or "my OKRs"' — and labels itself RECOMMENDED, plus notes 'no IDs needed' which implicitly contrasts with ID-driven siblings. It stops short of naming the alternative tool or stating when NOT to use it, so it is not a full when/when-not treatment.

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