Flowsery

Get Visitors by Operating System

get_operating_systems

Read-only

Get operating system distribution — Mac OS, Windows, iOS, Android, Linux, etc.

Input Schema

TableJSON Schema

Name	Required	Description
`endAt`	No	ISO 8601 end date (e.g. "2026-01-31")
`limit`	No	Max results (1-1000, default: 100)
`domain`	No	Website domain to query. Required when using a workspace token unless websiteId is provided.
`offset`	No	Pagination offset (default: 0)
`startAt`	No	ISO 8601 start date (e.g. "2026-01-01")
`timezone`	No	IANA timezone (e.g. "America/New_York"). Falls back to site default.
`filter_os`	No	Filter by operating system
`websiteId`	No	Website ID to query. Required when using a workspace token unless domain is provided.
`filter_ref`	No	Filter by ref URL parameter
`filter_via`	No	Filter by via URL parameter
`filter_city`	No	Filter by city
`filter_goal`	No	Filter by goal name
`filter_page`	No	Filter by page path
`filter_device`	No	Filter by device type: desktop, mobile, tablet
`filter_region`	No	Filter by region
`filter_source`	No	Filter by source URL parameter
`filter_browser`	No	Filter by browser name
`filter_channel`	No	Filter by marketing channel
`filter_country`	No	Filter by country
`filter_hostname`	No	Filter by hostname
`filter_referrer`	No	Filter by referrer domain
`filter_utm_term`	No	Filter by UTM term
`filter_entry_page`	No	Filter by entry/landing page
`filter_utm_medium`	No	Filter by UTM medium
`filter_utm_source`	No	Filter by UTM source
`filter_utm_content`	No	Filter by UTM content
`filter_utm_campaign`	No	Filter by UTM campaign

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	No	Operating systems with visitor counts.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

First observedSep 1, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, which covers the safety profile. The description adds the behavioral detail that results are a distribution across common operating systems, but it does not disclose details like pagination behavior, date-range handling, or whether results are counts or percentages. Given the annotations cover safety, this is adequate but not rich.

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 a single, focused sentence that immediately states the tool's purpose and gives helpful examples. There is no fluff or repetition of the title or schema.

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 analytics aggregation tool with a full schema, rich annotations, and an output schema, the description is adequate. It clearly defines what the returned data represents, and the schema handles the large parameter list. It could be improved with an explicit usage scenario or sibling differentiation, but nothing essential is missing.

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 fully documents all 27 parameters. The description adds no parameter-level meaning beyond the schema, which fits the baseline of 3 when structured data carries the load.

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 identifies the verb and resource: 'Get operating system distribution' with concrete examples of operating systems included. It is distinct from sibling tools like get_browsers or get_devices because the resource and intent are 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 the tool is used when an operating system breakdown is needed, and the title reinforces this. However, it does not explicitly state when to use this tool versus similar analytics tools, nor does it mention any exclusions or prerequisites.

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

All Flowsery tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0

Disambiguation5/5

Each tool serves a distinct purpose: get_* tools cover different analytics dimensions (browsers, cities, countries, etc.) with clear scopes, while issue management and tracking tools are clearly separated. Even get_breakdown is explicitly scoped to dimensions without dedicated endpoints, avoiding overlap.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with snake_case (delete_goals, get_overview, track_goal, update_issue_status). Verbs are specific and predictable (get, delete, track, list, update), and there are no naming style mixes.

Tool Count2/5

At 27 tools, the set exceeds the 25-tool threshold considered 'too many.' While the domain is broad (analytics, tracking, issues), many get_* tools could be consolidated into get_breakdown with filter parameters, making the count feel inflated rather than necessarily well-scoped.

Completeness4/5

The tool surface covers the full analytics lifecycle: overview, time series, breakdowns, real-time data, visitor profiles, goal/payment tracking and deletion, plus AI issue listing/detail/status updates. Minor gaps exist (e.g., no update for goals/payments, no explicit list of defined goals), but these are non-critical and don't impair typical workflows.

Resources

Need Help?