hdls Goals
hdls Goals is a headless, MCP-native goals & okrs backend. It manages objectives, key results, and check-ins, operated entirely through named tools your AI assistant calls. It stands in for tools like Weekdone, Gtmhub — same job, no UI to run.
💬 Just ask
"Add an objective to grow revenue, then show me my objectives."
You don't call these tools yourself — just tell your assistant in plain English. Everything below is the reference for when you (or your assistant) want the exact details.
How Goals is organized
The headline entity is the objective — start there, then attach the rest to it. Records connect by reference: a key_result links to an objective. The check_in table is an append-only timeline — every change and note lands there and is never edited or deleted.
| Entity | Purpose | Relates to |
|---|---|---|
objective | A qualitative goal; parent_id aligns it up to a higher objective. | cycle |
cycle | Planning period (e.g. a quarter) that objectives are scoped to. | — |
key_result | Measurable result under an objective; progress derives from start/current/target. | objective |
check_in | Append-only progress timeline: periodic confidence + value updates on objectives/key results. | objective, key_result |
Common workflows
Each line is one real sequence of tool calls — your assistant chains them for you.
- Set up an objective end to end:
create_objective→add_key_result
Tools
Call these at https://hdls.ai/api/mcp/okrs. Required fields you must supply; optional fields refine the call. You never pass tenant_id — it is stamped server-side.
Create
| Tool | What it does | Required | Optional |
|---|---|---|---|
create_objective | Create a new objective. | title | cycle_id, parent_id, description, owner, level, status |
Update & advance
| Tool | What it does | Required | Optional |
|---|---|---|---|
add_key_result | Add a key result. | objective_id, title | metric_type, start_value, target_value, current_value, unit, status |
update_progress | Update the progress of an objective by id. | id | progress |
align_goal | Align a goal to a parent. | id | — |
Find & read
| Tool | What it does | Required | Optional |
|---|---|---|---|
search_objectives | Search objectives by free-text and/or column filters (tenant-scoped, paginated). | — | search, filters, limit, orderBy |
Field lists come from the product's live schema and are embedded in each tool's own description — read the tool description for the exact, current fields.
Field reference
Every field you can set on each record. Custom fields you add live alongside these in data.
objective
| Field | Type | Required | Notes |
|---|---|---|---|
cycle_id | id | Links to a cycle. | |
parent_id | id | Reference to a related record. | |
title | text | Yes | Display name. |
description | text | ||
owner | text | ||
level | text | ||
status | text | Lifecycle state. | |
progress | numeric(5,2) | ||
data | json | Free-form JSON — custom fields live here. |
cycle
| Field | Type | Required | Notes |
|---|---|---|---|
name | text | Yes | Display name. |
start_date | date | ||
end_date | date | ||
status | text | Lifecycle state. | |
data | json | Free-form JSON — custom fields live here. |
key_result
| Field | Type | Required | Notes |
|---|---|---|---|
objective_id | id | Yes | Links to an objective. |
title | text | Yes | Display name. |
metric_type | text | ||
start_value | numeric(18,4) | ||
target_value | numeric(18,4) | ||
current_value | numeric(18,4) | ||
unit | text | ||
status | text | Lifecycle state. | |
owner | text | ||
data | json | Free-form JSON — custom fields live here. |
Tailor it with custom fields
Add fields without a schema change. add_custom_field defines one, list_custom_fields shows what's defined, and promote_custom_field (admin) shares a personal field with the whole workspace. The value lives in each row's data (JSON) and is set and read through the normal record tools. See Products, tools & custom fields for the full model.
Roles & safety
- Tenant isolation is automatic. Your credential is pinned to one workspace; you never pass
tenant_id, and you can only ever see your own data (enforced by Postgres row-level security). - Role-gated. Permissions run
reader < member < admin < owner. Installing a product and promoting a custom field workspace-wide need admin/owner. - History is append-only. The
check_intimeline is never edited or deleted — it's your audit trail.
Connect
On the concierge (https://hdls.ai/api/mcp), run install_product({ slug: "okrs" }) (admin/owner) to enable it for your workspace, then add https://hdls.ai/api/mcp/okrs as a connector in your assistant — see Connect your assistant.
A worked example
The literal call your assistant makes when you ask it to create the headline record:
Tool: create_objective
Arguments: {
"title": "Grow ARR to $1M"
}