findtime.io MCP Server

Check who is awake

are_they_awake

Read-onlyIdempotent

Reports whether people in other cities are within work, awake, or sleep hours at a specified moment. myTime defaults to now. myTimezone accepts an IANA zone; myCity supplies location context when myTimezone is omitted. The result includes formatted shareText and may include a plannerUrl with alternative aiSlots.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "are_they_awake"
  }
}

Input Schema

Name	Required	Description
`date`	No	YYYY-MM-DD when myTime is only a clock time.
`myCity`	No	Caller city, used when myTimezone is omitted.
`myTime`	No	ISO instant, or a floating local time in myTimezone. Defaults to now.
`teamId`	No	Exact homepage Saved group name. A signed-in hosted agent loads that group when their cities are omitted. Marketing and marketing are two groups. Without an account, returns teams_not_persisted.
`workEnd`	No	Last in-hours local hour, inclusive. Default 18.
`locations`	No
`theirCity`	No	One city or timezone to judge.
`workStart`	No	First in-hours local hour. Default 9.
`_endUserId`	No	Optional opaque per-call end-user attribution token populated by the MCP host, not the LLM. Accepts a non-PII hash or token, excluding raw email addresses, names, or platform user IDs.
`myTimezone`	No	IANA timezone for the caller, such as America/Los_Angeles.
`theirCities`	No
`durationMinutes`	No	Optional. Only 30, 45, or 60 are written onto the planner link.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive safety. The description adds useful context beyond them: myTime defaults to now, work hours default to 9–18 via the schema, and the result includes formatted shareText and may include a plannerUrl with alternative aiSlots, which tells the agent what it can do with the output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, front-loaded with the core behavior and zero filler. Defaults and return-shape notes follow in a logical order, though the parameter notes are slightly scattered relative to a clean when-to-use statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter tool with no output schema, the description adequately covers the return payload and key defaults. However it never defines how 'awake' and 'sleep' windows are derived (only workStart/workEnd exist as parameters), which is central to interpreting results.

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 coverage is 83%, so the schema already documents most parameters, including the myCity-when-myTimezone-omitted relationship and the myTime default that the description restates. The description adds little new semantics and leaves the 'awake' vs 'sleep' boundary definition unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: reports whether people in other cities fall in work, awake, or sleep hours at a given moment. An agent can tell it apart from time conversion or slot-finding siblings by the 'is this person available right now' framing, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the purpose statement — an agent infers this is a pre-scheduling sanity check. There is no explicit guidance on when to prefer this over get_overlap_hours, time_snapshot, or find_meeting_time, and no stated prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All findtime.io MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.