Strety

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. Before calling this tool, confirm the title and content (or template choice) with the user.

Create a new headline in a team, person, or project space. 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. Before calling this tool, confirm the exact title and description with the user.

Create a new issue in a team, person, or project space. 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. Before calling this tool, confirm the exact title and description with the user.

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. Drafts cannot be published through MCP — when creating a draft, give the user the returned permalink and tell them to open it to review and post the message from the web app. Before calling this tool, confirm the exact title and content with the user.

Create a new metric (measurable) on a team, person, or project scorecard. 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. Before calling this tool, confirm the exact title and target with the user.

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. Use update_project to rename a project or change who is on it. Before calling this tool, confirm the title with the user.

Create a new rock (90-day priority) in a team, person, or project space. 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. Use checkin_rock to record progress after creation. Before calling this tool, confirm the exact title and details with the user.

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. Before calling this tool, confirm the recipients, core values, and message with the user.

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. 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. Before calling this tool, confirm the name with the user.

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. Before calling this tool, confirm the final title and description with the user.

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.

Get a top-down view of the company: basics, vision summary, current quarter company rocks, company scorecard, and teams list. Provides full organizational context in one call. For the full vision document use get_vto. For the public company-wide Accountability Chart use get_accountability_chart.

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, 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, and comments — everything in one call. Use list_issues to discover issue IDs.

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

Get a meeting's full context as markdown. 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.

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, 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, 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, department, 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.

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.

Get a rock's full context: title, status, backlog state, assignee, due date, description, milestones, recent check-ins, related resources, and comments — everything in one call. Use list_rocks to discover rock IDs, and get_milestone for one milestone's full context.

Get a shoutout's full context: creator, recipients, recognized core values, content, and comments — everything in one call. Use list_shoutouts to discover shoutout IDs.

Get a team's overview: name, description, members, and enabled tools. Provides full context about a team space. Use list_teams to discover team IDs.

Get a todo's full context: title, status, assignee, description, custom field values, checklist, related resources, and comments — everything in one call. Use list_todos to discover todo IDs.

Get the company's Vision/Traction Organizer: core values, core focus, 10-year target, 3-year picture, 1-year plan, quarterly rocks, strategy, and SWOT analysis. Provides strategic context for all EOS work. For a broader org snapshot (teams, scorecard) use get_company.

List docs. Omit team_id, person_id, and project_id to list docs at the company level; pass one to list a team, person, or project space's docs. Returns the catalog for the selected scope: folder structure and every doc with its folder path and comment count. Published docs only by default — pass status_in to include your own drafts. Use get_doc to read full content.

List headlines in a team, person, or project. Returns summary info for each headline. Provide exactly one of team_id, person_id, or project_id. Use get_headline for full context including description and comments. Pass `next_cursor` from the previous response to fetch the next page. Iteration is complete when `next_cursor` is absent.

List issues in a team, person, or project. Returns summary info for each issue. Provide exactly one of team_id, person_id, or project_id. Use get_issue for full context. Use create_issue to add new issues, comment_on_resource to comment, or resolve_issue to mark resolved. Pass `next_cursor` from the previous response to fetch the next page. Iteration is complete when `next_cursor` is absent.

List meetings (L10s, quarterlies, 1:1s, custom, etc.) in a team, person, or project. Returns summary info for each meeting. Provide exactly one of team_id, person_id, or project_id. Use get_meeting for full context including attendees, agenda, notes, and recap. Pass `next_cursor` from the previous response to fetch the next page. Iteration is complete when `next_cursor` is absent.

List messages. Omit team_id, person_id, and project_id to list messages posted at the company level; pass one to list a team, person, or project space's messages. Returns summary info for each message. Use get_message for full message content, comments, and activity. Pass `next_cursor` from the previous response to fetch the next page. Iteration is complete when `next_cursor` is absent.

List metrics (measurables) in a team, person, or project scorecard. Returns each metric's title, assignee, target, frequency, current status (on track, off track, or not checked in), and scorecard category, plus the scorecard's available categories — use a category id with create_metric or update_metric to categorize a metric. Provide exactly one of team_id, person_id, or project_id. Pass `next_cursor` from the previous response to fetch the next page. Iteration is complete when `next_cursor` is absent.

List notifications for the current user, grouped by the record they relate to. Defaults to unread. Use get_recent_notifications for a rich markdown summary of what needs attention. This tool returns structured data for pagination and filtering by read status. Pass `next_cursor` from the previous response to fetch the next page. Iteration is complete when `next_cursor` is absent.

List people. Omit team_id and project_id to list everyone in the company; pass one to list only that space's members. Pass the returned id as person_id to list_todos and other space-scoped tools. Pass `next_cursor` from the previous response to fetch the next page.

List projects the current person can access. Returns each project's id and name. Pass the id as project_id to list_todos and other space-scoped tools.

List rocks (90-day priorities). Omit team_id, person_id, and project_id to list rocks owned at the company level; pass one to list a team, person, or project space's rocks. To find rocks anywhere in the org that are flagged as visible-at-the-company-level (a per-rock setting), pass `company_wide_eq: true` instead — see that filter for details. Returns summary info for each rock, including whether it is backlogged. Use get_rock for full context including description, milestones, check-ins, and comments. Pass `next_cursor` from the previous response to fetch the next page. Iteration is complete when `next_cursor` is absent.