{"openapi":"3.1.0","info":{"title":"Remoteteam API","version":"0.1.0","description":"A fully local distributed/remote-team management reference: a real timezone-overlap-window calculator, async-communication norms, a meeting-vs-async decision framework, a remote-onboarding checklist, and a distributed-team-culture-building reference.\n\nEvery operation is read-only or compute-only. The same tools are available over MCP (streamable HTTP) at https://remoteteam.connectorbay.com/mcp.","contact":{"name":"Unify Dynamics LLC","email":"hr@unifydynamics.com","url":"https://connectorbay.com/remoteteam/docs"},"termsOfService":"https://connectorbay.com/remoteteam/terms"},"servers":[{"url":"https://remoteteam.connectorbay.com"}],"externalDocs":{"url":"https://connectorbay.com/remoteteam/docs"},"security":[{},{"bearer":[]}],"components":{"securitySchemes":{"bearer":{"type":"http","scheme":"bearer","description":"Optional. A Pro API key raises rate limits; no credentials are required."}},"schemas":{"Error":{"type":"object","properties":{"ok":{"const":false},"error":{"type":"object"}}}}},"paths":{"/v1/tools/timezone_overlap_window":{"post":{"operationId":"timezone_overlap_window","summary":"Computes the real overlapping working-hours window(s) in UTC across 2+ team members' timezones and","description":"Computes the real overlapping working-hours window(s) in UTC across 2+ team members' timezones and\n    local work hours, correctly handling DST (for IANA zone names) and midnight wraparound. Reports zero\n    overlap honestly when there is none. Use for \"what hours overlap across our team's timezones\", \"find a\n    meeting time that works for everyone\".","tags":["tools"],"requestBody":{"required":true,"content":{"application/json":{"schema":{"properties":{"members":{"description":"2+ members, each: {name, timezone, work_start, work_end}. timezone: IANA name (preferred) or numeric UTC offset like '+5:30'. work_start/work_end: HH:MM 24h, default 09:00-17:00.","items":{"additionalProperties":true,"type":"object"},"minItems":2,"title":"Members","type":"array"},"reference_date":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"ISO date (YYYY-MM-DD) to resolve IANA DST offsets against. Defaults to today.","title":"Reference Date"},"resolution_minutes":{"default":15,"description":"Scan resolution: 5, 10, 15, 20, 30, or 60.","title":"Resolution Minutes","type":"integer"}},"required":["members"],"title":"timezone_overlap_windowArguments","type":"object"}}}},"responses":{"200":{"description":"Tool result. `ok: true` on success; `ok: false` with a structured `error` (provider_unavailable, upstream_error, bad_input) when the tool could not answer.","content":{"application/json":{"schema":{"type":"object","additionalProperties":true}}}},"422":{"description":"Arguments failed validation","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"429":{"description":"Rate limit exceeded (see Retry-After)","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}},"x-read-only":true}},"/v1/tools/async_communication_norms":{"post":{"operationId":"async_communication_norms","summary":"Urgency-tiered response-time expectations (urgent/blocking, normal, FYI) and norms for documenting","description":"Urgency-tiered response-time expectations (urgent/blocking, normal, FYI) and norms for documenting\n    decisions in writing, writing for a time-shifted reader, and treating silence within the agreed window\n    as normal. Use for \"what response time should we expect on Slack\", \"how should we document decisions\".","tags":["tools"],"requestBody":{"required":true,"content":{"application/json":{"schema":{"properties":{},"title":"async_communication_normsArguments","type":"object"}}}},"responses":{"200":{"description":"Tool result. `ok: true` on success; `ok: false` with a structured `error` (provider_unavailable, upstream_error, bad_input) when the tool could not answer.","content":{"application/json":{"schema":{"type":"object","additionalProperties":true}}}},"422":{"description":"Arguments failed validation","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"429":{"description":"Rate limit exceeded (see Retry-After)","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}},"x-read-only":true}},"/v1/tools/meeting_vs_async_decision":{"post":{"operationId":"meeting_vs_async_decision","summary":"A decision framework for what should be a live meeting versus handled asynchronously, with reasoning","description":"A decision framework for what should be a live meeting versus handled asynchronously, with reasoning\n    for each situation type. Use for \"should this be a meeting or can it be async\", \"do we need a call for\n    this status update\".","tags":["tools"],"requestBody":{"required":true,"content":{"application/json":{"schema":{"properties":{"situation_keyword":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"A keyword or short phrase, e.g. 'brainstorm', 'status update', 'sensitive feedback'. Omit for the full table.","title":"Situation Keyword"}},"title":"meeting_vs_async_decisionArguments","type":"object"}}}},"responses":{"200":{"description":"Tool result. `ok: true` on success; `ok: false` with a structured `error` (provider_unavailable, upstream_error, bad_input) when the tool could not answer.","content":{"application/json":{"schema":{"type":"object","additionalProperties":true}}}},"422":{"description":"Arguments failed validation","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"429":{"description":"Rate limit exceeded (see Retry-After)","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}},"x-read-only":true}},"/v1/tools/remote_onboarding_checklist":{"post":{"operationId":"remote_onboarding_checklist","summary":"A checklist of remote-specific onboarding logistics by phase: equipment/access provisioning before","description":"A checklist of remote-specific onboarding logistics by phase: equipment/access provisioning before\n    day 1, a synchronous welcome and access verification on day 1, 1:1 video intros and an early real task\n    in the first two weeks, and cross-team exposure in the first 90 days. Use for \"give me a remote\n    onboarding checklist\".","tags":["tools"],"requestBody":{"required":true,"content":{"application/json":{"schema":{"properties":{"phase":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"'before day 1' | 'day 1' | 'first 2 weeks' | 'first 90 days'; omit for all phases.","title":"Phase"}},"title":"remote_onboarding_checklistArguments","type":"object"}}}},"responses":{"200":{"description":"Tool result. `ok: true` on success; `ok: false` with a structured `error` (provider_unavailable, upstream_error, bad_input) when the tool could not answer.","content":{"application/json":{"schema":{"type":"object","additionalProperties":true}}}},"422":{"description":"Arguments failed validation","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"429":{"description":"Rate limit exceeded (see Retry-After)","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}},"x-read-only":true}},"/v1/tools/distributed_team_culture_guide":{"post":{"operationId":"distributed_team_culture_guide","summary":"A reference on building culture on a distributed team: protecting shared overlap time, engineering","description":"A reference on building culture on a distributed team: protecting shared overlap time, engineering\n    low-stakes social space, documenting rituals/norms, visible async-friendly recognition, rotating\n    meeting-time pain across timezones, and periodic higher-bandwidth touchpoints. Use for \"how do we build\n    culture on a remote team\".","tags":["tools"],"requestBody":{"required":true,"content":{"application/json":{"schema":{"properties":{"topic_keyword":{"anyOf":[{"type":"string"},{"type":"null"}],"default":null,"description":"A keyword to filter, e.g. 'recognition', 'overlap', 'rituals'. Omit for the full list.","title":"Topic Keyword"}},"title":"distributed_team_culture_guideArguments","type":"object"}}}},"responses":{"200":{"description":"Tool result. `ok: true` on success; `ok: false` with a structured `error` (provider_unavailable, upstream_error, bad_input) when the tool could not answer.","content":{"application/json":{"schema":{"type":"object","additionalProperties":true}}}},"422":{"description":"Arguments failed validation","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}},"429":{"description":"Rate limit exceeded (see Retry-After)","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Error"}}}}},"x-read-only":true}}}}