Sensor Bio MCP Server

Official

by GetSensr-io

Overview Schema Source Related Servers Discussions Admin

Python

Remote

get_biometrics

Retrieve biometric data for a user, with optional date and timestamp filters to narrow results by time range.

Instructions

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

Params:

user_id (str, required)
start_date/end_date (YYYY-MM-DD, optional)
start_timestamp_ms/end_timestamp_ms (int, optional)
cursor (str, optional)
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_biometrics"
  }
}

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?

With no annotations, the description carries the full burden. It discloses pagination behavior via the 'cursor' parameter and return fields (next_cursor, has_more, next_url), and it specifies optional filtering with date/timestamp. However, it does not mention authentication requirements, rate limits, or behavior on invalid inputs, leaving some gaps in transparency.

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 succinct and well-structured: a one-sentence purpose followed by a bulleted parameter list and a clear return format. Every line provides essential information without redundancy or padding.

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?

Given the tool has 8 parameters and no annotations, the description provides a complete picture of the request and response shape. It includes pagination, optional filters, and the exact return object. Minor gaps exist, such as interaction between date and timestamp filters or any maximum limit, but overall it is 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 schema description coverage is 0%, so the description must compensate. It does so by listing all parameters with types, requiredness, defaults, and date format (YYYY-MM-DD). This adds meaningful context beyond the bare schema, such as limit default 50 and optional cursor for pagination.

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 a specific action ('Get biometrics for a user') with an optional scope of date/timestamp filtering. This distinguishes it from sibling tools like get_sleep or get_scores, which target different data types. The verb 'get' plus the resource 'biometrics' is unambiguous.

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 when biometrics are needed but does not explicitly contrast with alternatives or provide when-not conditions. For example, it does not say to use a sibling tool for sleep or scores. The context is clear from the tool name, but explicit guidance for choice among siblings is absent.

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

Deploy Server