Skip to main content
Glama
Sign In
fulcradynamics

Fulcra MCP Server

by fulcradynamics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get Time Series

get_time_series
Read-only

Retrieve calculated per-interval time-series values for a single data type across a time range, optionally adjusting sample rate and per-slice calculations.

Instructions

Get calculated per-interval time-series values for a single data type.

Only data types that get_data_catalog lists as usable with this tool are supported; other types can be read with get_records. Result timestamps include time zones; translate them to the user's local time zone when known.

Input Schema

NameRequiredDescriptionDefault
end_timeYesRange end (exclusive). Must include tz (ISO8601).
data_typeYesThe data type ID to retrieve (see `get_data_catalog`).
start_timeYesRange start (inclusive). Must include tz (ISO8601).
sample_rateNoSeconds per sample; may be fractional.
calculationsNoExtra per-slice calculations to include. One or more of "max", "min", "delta", "mean", "uniques", "allpoints", "rollingmean". Not supported on "cumulative" kinds.
fulcra_useridNoRetrieve data for another Fulcra user (if shared); a shared type's get_data_catalog entry carries its owner's ID.
replace_nullsNoReplace missing values (NA) with 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed12 schema fields changedv1.18.7
    • removedInput schema / properties / calculations / anyOf
      Removed value: -[
-  {
-    "items": {
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / calculations / default
      Removed value: -null
    • addedInput schema / properties / calculations / items
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / calculations / type
      Added value: +"array"
    • removedInput schema / properties / fulcra_userid / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • removedInput schema / properties / fulcra_userid / default
      Removed value: -null
    • addedInput schema / properties / fulcra_userid / type
      Added value: +"string"
    • removedInput schema / properties / replace_nulls / anyOf
      Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / replace_nulls / type
      Added value: +"boolean"
    • removedInput schema / properties / sample_rate / anyOf
      Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedInput schema / properties / sample_rate / type
      Added value: +"number"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "type": "object",
-  "x-fastmcp-wrap-result": true
-}New value: +null
  2. Addedv1.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context: only catalog-listed types work, result timestamps include time zones, and callers should translate to the user's local time when known. It does not describe return shape or pagination, keeping it from a 5.

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?

Three tight sentences, front-loaded with purpose and followed by eligibility constraints and timestamp handling advice. Every sentence adds useful information with no filler.

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?

For a read-only tool with seven well-described parameters and safety annotations, the description covers purpose, supported data types, fallback behavior, and time zone handling. Because there is no output schema, the response shape is only implied rather than fully described, so it is strong but not maximally complete.

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 description coverage is 100%, so the schema already documents all seven parameters, including time zone requirements for start_time and end_time. The description does not add parameter-level detail beyond what the schema provides, so the baseline 3 is appropriate.

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?

States a specific verb, resource, and scope: 'Get calculated per-interval time-series values for a single data type.' It also distinguishes this tool from get_records for unsupported data types, so an agent can select it without opening the schema.

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

Usage Guidelines5/5

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

Explicitly says only data types listed by get_data_catalog as usable with this tool are supported, and directs other types to get_records. This gives clear when-to-use and when-not-to-use guidance with a named alternative.

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

Deploy Server

Other Tools