Skip to main content
Glama
GetSensr-io

Sensor Bio MCP Server

Official
by GetSensr-io

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}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
cursorNo
user_idYes
end_dateNo
start_dateNo
last_timestampNo
end_timestamp_msNo
start_timestamp_msNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It explains that the tool returns data with pagination (cursor, has_more, next_url) and filtering options. However, it does not mention side effects, permissions, rate limits, or error handling. The return format is partially described, but lacks detail on the data structure.

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. It leads with the main purpose, then lists parameters in a bullet-like format, and ends with the return structure. Every sentence adds value without redundancy.

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?

Given the tool has 8 parameters and an output schema, the description explains filtering and pagination but lacks explanation of what activities represent, potential errors, or limitations. It also misses the 'last_timestamp' parameter. For moderate complexity, it is adequate but not thorough.

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 significant meaning to most parameters beyond the schema: formats for dates (YYYY-MM-DD), default for limit (50), and optional/required status. However, it omits the 'last_timestamp' parameter present in the schema, leaving a gap. Schema coverage is 0%, so the description carries the full burden; it covers 7 of 8 parameters well.

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?

The description clearly states the tool gets activities for a user with optional filtering. It specifies the resource ('activities') and the filtering options, but does not explicitly differentiate from sibling tools like get_sleep or get_biometrics. However, the verb+resource combination is specific enough for most agents.

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

Usage Guidelines2/5

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

The description does not provide guidance on when to use this tool versus alternatives. It does not mention when not to use it or list sibling tools for comparison. The agent must infer usage from the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/GetSensr-io/sensorbio-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server