Skip to main content
Glama

Flowsery

by com.flowsery

Get Live Visitor Map

get_realtime_map
Read-only

Get currently active visitors with geographic location data for map visualization.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoWebsite domain to query. Required when using a workspace token unless websiteId is provided.
websiteIdNoWebsite ID to query. Required when using a workspace token unless domain is provided.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoCurrently active visitors with their geographic locations.

Schema Changelog

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

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already communicate that the tool is read-only and non-destructive. The description adds that it targets currently active visitors with geographic data, but does not disclose behavioral details such as authentication context, rate limits, or response shape. This is acceptable given the readOnlyHint, though not especially 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 sentence that front-loads the core action and purpose. There is no filler, repetition, or unusable detail.

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 low-complexity, read-only tool with a full output schema and well-described optional parameters, the description is nearly sufficient. It could mention alternate usage scenarios or clarify that the response is location data rather than a rendered map, but the output schema covers return details.

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%, and both domain and websiteId already have clear descriptions. The tool description itself adds no parameter semantics, so the baseline score of 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?

The description states a specific verb and resource: "Get currently active visitors with geographic location data." It also clarifies the intended use case, "for map visualization," which makes the tool's purpose unambiguous and distinct from unrelated sibling tools.

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 use when a live geographic visitor map is needed, but gives no explicit guidance about when to prefer this tool over alternatives or when not to use it. The schema covers parameter requirements, but the description itself lacks direct sibling differentiation.

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

All Flowsery toolsInspect
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