Sensor Bio MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

get_activities

Retrieve user activity records with optional date or timestamp filters. Supports pagination via cursor to navigate results.

Instructions

Get activities for a user with optional date/timestamp filtering.

Params:

user_id (str, required)
start_date/end_date (YYYY-MM-DD, optional): filter by activity timestamp
start_timestamp_ms/end_timestamp_ms (int, optional): filter by ms since epoch
cursor (str, optional): pagination cursor
limit (int, default 50)

Returns: {data, next_cursor, has_more, next_url}

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "user_id": "<user_id>"
    },
    "name": "get_activities"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`cursor`	No
`user_id`	Yes
`end_date`	No
`start_date`	No
`last_timestamp`	No
`end_timestamp_ms`	No
`start_timestamp_ms`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 30, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses optional filtering, pagination via cursor, and the return shape. However, it does not mention ordering, authentication needs, rate limits, or potential side effects, leaving some behavioral transparency gaps.

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

Conciseness5/5

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

The description is concise and well-structured: a one-line summary, a bulleted parameter list, and a returns line. Every sentence provides value and does not repeat the schema verbatim.

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

Completeness4/5

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

The description provides core invocation details (user_id, filters, pagination) and return fields, making it largely complete. However, the missing last_timestamp parameter and lack of usage alternatives leave gaps for a tool with 8 parameters and no schema descriptions, so it is not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds meaning beyond the schema for most parameters, explaining date/timestamp filter formats, cursor as pagination, and limit default. However, it completely omits the last_timestamp parameter that exists in the schema, and it does not clarify whether date and timestamp filters can be combined, leaving some semantic ambiguity.

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

Purpose5/5

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

The description clearly states 'Get activities for a user with optional date/timestamp filtering.' This gives a specific verb, resource, and scope, and distinguishes it from sibling tools like get_sleep, get_scores, and get_biometrics, which target different data types.

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?

The description implies usage for retrieving a user's activities, but it does not provide explicit when-to-use guidance, exclusions, or alternatives among the sibling tools. There is no mention of when to prefer this over get_biometrics or other get_* tools, so guidance is only implicit.

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

Deploy Server