Strety

Mark a rock's milestone done or reopen it. Use get_rock to see milestones and their IDs; use update_milestone to change its title, date, or owner.

Mark a todo as complete or incomplete. Use list_todos to find todo IDs. Optionally add a comment when completing (e.g. to explain the outcome or provide context).

Create a new check-in: a question asked to a team, person, or project space (or company-wide) on a recurring schedule. Provide team_id, person_id, or project_id to specify where it belongs, or omit all three for a company-wide check-in. Use list_teams, list_people, or list_projects to find valid space IDs. Defaults to asking every non-viewer member of the space, weekly on weekdays at 9am in the caller's time zone. Use update_check_in to change the schedule or participants later.

Answer a check-in question. Use list_check_ins to discover check_in IDs.

Create a core process in a team's space: one of the few documented, repeatable ways the business runs, such as hiring or sales. Pass the team_id of the team to create it in. Title is required. It is owned by you unless owner_id is passed (a person ID from list_people); the owner must be a member of the space, and if you are not, it has no owner. The owner is subscribed to it. Pass subprocesses, each with optional steps, to create the whole outline in one call; if anything is invalid nothing is created. Use create_subprocess and create_step to add to a core process that already exists. Edits change the working copy only; a published core process's published version changes only when an admin publishes a new version in Strety. Returns the created core process with its sub-processes and steps.

Create a doc in a team, person, or project space. Provide exactly one of team_id, person_id, or project_id (use list_teams / list_people / list_projects for IDs). Provide a title (and optional content) to create a doc from scratch, or a template_id from list_templates(type: "doc") to seed it from a template, not both. Pass a folder_id from list_docs to create the doc inside that folder; omit it to create the doc at the top level of the space's docs. From-scratch docs are saved as drafts unless publish: true is passed; docs created from a template are always published. When creating a draft, give the user the returned url so they can review it — publish it later with update_doc (publish: true) when they ask, or they can publish from the web app.

Create a folder for docs in a team, person, or project space. Provide exactly one of team_id, person_id, or project_id. Pass a parent_id from list_docs to nest the folder inside another folder; omit it to create the folder at the top level. Returns the new folder's id: pass it as folder_id to create_doc or update_doc to put docs in it.

Create a new headline in a team, person, or project space. A headline is a short piece of customer or employee news, good or bad, shared in the meeting without discussion. Anything that needs discussion is an issue. Provide exactly one of team_id, person_id, or project_id to specify where the headline belongs. Use list_teams, list_people, or list_projects to find valid space IDs. Title is required.

Create a new issue in a team, person, or project space. An issue is anything unresolved: a problem, obstacle, opportunity, or idea the team needs to identify, discuss, and solve. It states what is wrong or open, not the fix. If the action is already agreed, that is a todo. Provide exactly one of team_id, person_id, or project_id to specify where the issue belongs. Use list_teams, list_people, or list_projects to find valid space IDs. Title is required.

Create a new message in a team, person, or project space. Provide exactly one of team_id, person_id, or project_id to specify where the message belongs. Use list_teams, list_people, or list_projects to find valid space IDs. Title is required. Defaults to publishing immediately, which notifies subscribers; pass publish: false to leave it as a draft. When creating a draft, give the user the returned url so they can review it — publish it later with update_message (publish: true) when they ask, or they can post it from the web app.

Create a new metric (measurable) on a team, person, or project scorecard. A measurable is one weekly, activity-based number with one owner and a goal, on a scorecard of 5-15. Leading indicators (what the team does) over lagging results (what happened). Provide exactly one of team_id, person_id, or project_id to specify which scorecard the metric belongs to. Use list_teams, list_people, or list_projects to find valid space IDs. Title is required; the metric defaults to a weekly, plain-number measurable owned by the current user with a "greater than or equal to" goal, so target_value is required. For a range goal, pass target_type 'between' along with target_min_value and target_max_value. Use checkin_metric to record values after creation.

Add a milestone to a rock. Milestones break a quarterly rock into the checkpoints that show it is on track before the due date arrives, so each one names a deliverable with a date the owner can tick off. Give the rock and a title; the milestone is unassigned and undated unless you say otherwise. Use list_rocks to find rock IDs and get_rock to see a rock's existing milestones. Use complete_milestone to mark one done, and get_milestone for one milestone's full context.

Create a new project in the current organization. Title is required. Optionally pass a template_id to seed the project from a project template (use list_templates type: "project" to discover IDs; template content is materialized asynchronously). When template_id is provided, the template controls privacy and description — explicit values for those fields are ignored. You are always added as a member; pass person_ids to add others at the same time, using list_people to find person IDs. Use update_project to rename a project or change who is on it.

Create a new rock in a team, person, or project space. A rock is one of a team's 3-7 most important priorities for the quarter, judged Done or Not Done at quarter end, so it is specific and measurable with one owner. Work that fits in a week is a todo; something unresolved is an issue. Provide exactly one of team_id, person_id, or project_id to specify where the rock belongs. Use list_teams, list_people, or list_projects to find valid space IDs. Title is required; the rock defaults to a binary (on/off-track) rock owned by the current user, due at the end of the quarter. For a measurable rock, pass check_in_type 'with_target' along with start_value, target_value, and value_format. Pass backlogged: true to create a planned rock in the backlog. Pass milestones to break the rock into checkpoints as it is created; the response returns them with their IDs on the rock, so update_milestone can date or assign one afterwards. Use checkin_rock to record progress after creation.

Add a seat to an Accountability Chart, reporting to an existing seat on that chart. Seat IDs come from get_accountability_chart, and assignee IDs from list_people. A seat can't report to the Owner's Box, or to the Visionary when the Visionary and Integrator sit side by side. Use add_seat_role to give the new seat its roles.

Create a new shoutout (peer recognition) in a team, person, or project space, or company-wide. Provide team_id, person_id, or project_id to specify where the shoutout belongs, or omit all three for company-wide recognition. Use list_teams, list_people, or list_projects to find valid space IDs. Shoutouts require at least one recipient and at least one recognized core value. Pass company_shoutout: true to surface a team/person/project shoutout to the whole company.

Add a step to a sub-process: one concrete action in how the work gets done. Title is required. The step is added after the existing steps. Edits change the working copy only; a published core process's published version changes only when an admin publishes a new version in Strety. Returns the created step. Sub-process IDs come from get_core_process.

Add a sub-process to an existing core process: one stage of how the core process runs, such as interviewing within hiring. Title is required. It is added after the existing sub-processes, in the core process's space, in the 'identify' phase unless phase is passed, and owned by the core process's owner unless owner_id is passed (a person ID from list_people; the owner must be a member of the space). Pass steps to create its steps in the same call, or add them later with create_step; if anything is invalid nothing is created. Edits change the working copy only; a published core process's published version changes only when an admin publishes a new version in Strety. Returns the created sub-process with its steps.

Create a new team in the current organization. The name must be unique across the organization's teams. New teams start with the organization's standard tools enabled and their default meetings scheduled. You are always added as a member; pass person_ids to add others at the same time, using list_people to find person IDs. Use list_teams to see existing teams, or get_team for a team's full context. Use update_team to rename a team or change who is on it.

Create a new todo in a team, person, or project space. Provide exactly one of team_id, person_id, or project_id to specify where the todo belongs. Use list_teams, list_people, or list_projects to find valid space IDs. Either `title` or `template_id` is required. When `template_id` is given, the template's title, description, priority, and checklist seed the todo; any of those fields you also pass override the template defaults. Use list_templates(type: "todo") to discover template IDs. Custom fields can be set by name and option label via `custom_fields` — use get_team, get_person, or get_project to discover available fields and options for the space.

Create a new todo list in a team, person, or project space. Provide exactly one of team_id, person_id, or project_id, plus a title. The list is added after the space's other undocked lists and starts empty. Returns the list with its id; pass that id as todo_list_id to create_todo or move_todo to put todos in it.

Permanently delete a check-in answer. Unlike other resources, check-in answers have no trash and cannot be restored. Only the creator can delete their own answer. Use list_check_in_answers to discover check_in_answer IDs.

Get the public company-wide Accountability Chart. Returns the chart's reporting structure and every seat's assignees, purpose, roles, and role descriptions. This does not return private team Accountability Charts. Use create_seat and update_seat to change seats, and add_seat_role, update_seat_role, or remove_seat_role to change their roles.

Get a check-in's full context: its schedule, participants, and the most recent answers. Use list_check_in_answers for older answers beyond what's shown here. Use list_check_ins to discover check-in IDs.

Get a top-down view of the company: basics, current quarter dates, leadership team id, current quarter company rocks, company scorecard, and teams list. Provides full organizational context in one call. rocks and metrics are capped; rocks_count and metrics_count give the totals. For the V/TO use get_vto. For the public company-wide Accountability Chart use get_accountability_chart.

Get a core process's full context: title, owner, description, whether it is published and its latest published version, its sub-processes in order (each with phase, owner, description, and steps; a sub-process can live in another team's space, named in its `space`), the rocks and metrics it tracks, and comments, everything in one call. Returns the live record only, never a published version's contents, and omits sub-processes, rocks, and metrics you cannot access. Use list_core_processes to discover core process IDs. Use get_published_process for the published version's contents.

Read a doc's content and comments. Returns the document body for document-type docs, the URL for link-type, or the filename for uploads, along with the comment count and any comment threads (useful for ranking VoC requests by customer demand). Use list_docs to discover doc IDs.

Get a headline's full context: title, status, owner, description, related resources, subscribers, and comments — everything in one call. Use list_headlines to discover headline IDs.

Get an issue's full context: title, status, owner, description, resolution, related resources, subscribers, and comments — everything in one call. Use list_issues to discover issue IDs.

Get the authenticated user's identity and authorized organization memberships, including each organization's leadership team id. Use get_my_profile for their teams, projects, and working context within an organization.

Get a meeting's full context. For completed meetings, returns a recap: attendees, todos created, issues solved/opened, headlines, ratings, and notes. For upcoming meetings, returns a one-call prep brief: enriched agenda, open IDS issues (team meetings), and outstanding todos. Use list_meetings to discover meeting IDs. Agenda section IDs in the output can be passed to update_agenda_item and remove_agenda_item. When transcript_available is true, get_meeting_transcript returns the verbatim wording.

Get the verbatim transcript of a recorded meeting, as plain text. Often 10k+ tokens — call this only when the user asks for the exact wording or a direct quote. For attendees, todos, issues, decisions, or a recap, use get_meeting instead. Use list_meetings to discover meeting IDs.

Get a message's full context: content, subscribers, comments, related resources, and metadata. Use list_messages to discover message IDs.

Get a metric's full context: title, assignee, description, target, frequency, formula (for calculated metrics), recent check-in history, subscribers, and comment count. Values match the scorecard, including formula-computed values for calculated metrics. Use list_metrics to discover metric IDs.

Get a milestone's full context: title, completion, due date, assignee, description, the rock it belongs to, and the issues, todos and shoutouts created from it. A milestone URL ends in its ID, so a link pasted by the user resolves here. Use get_rock to see all of a rock's milestones and their IDs.

Get the authenticated person's profile: name, role, title, teams, projects, accountability chart seats, direct reports, manager, members, and enabled tools. Start here to understand who the current user is.

Get a person's profile: name, role, title, manager, teams, projects, accountability chart seats, direct reports, members, and enabled tools. Use list_people to discover person IDs.

Get a project's overview: title, status, progress, dates, description, members, and enabled tools. Provides full context about a project space. Use list_projects to discover project IDs.

Get one of the organization's published core processes ("The {Org} Way", the documented way the company runs): its latest published version with the sub-processes in order, each with its owner, description, and steps, plus the title, owner, space, and description as they are now. Visible to everyone in the organization except external users. Returns the latest published version only. Use list_published_processes to discover core process IDs. Use get_core_process for the live working copy, which may differ from what was published.

See what needs the current user's attention. Returns the 10 most recent unread notification groups as a markdown summary — each group represents a distinct record with a count of unread notifications, who triggered the latest one, and a link. For record types that have detail tools (Todo, Message, Metric, Project), the summary includes which tool to call for full context. Typically called after get_my_profile to see what needs the user's attention. Use list_notifications for paginated structured data or to browse read notifications.