Skip to main content
Glama

Get Logitech Sync environment report

logitech_sync_get_environment_report
Read-onlyIdempotent

Aggregate Spot/Rally Board sensor readings with numeric filters for CO2, temperature, humidity, and more. Returns device readings, timestamps, and per-metric averages.

Instructions

Aggregate Spot/Rally Board sensor readings with explicit numeric filters.

    Supported measurements include CO2, pressure, temperature, humidity, TVOC, VOC index,
    PM10, PM2.5, and presence. The workflow never invents safety thresholds or labels readings
    dangerous; filtering only occurs when ``metric`` and caller-provided bounds are supplied.

    Returns device readings, UTC sample timestamps, per-metric min/max/average, and scan status.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
desksNoInspect desk sensors.
roomsNoInspect room sensors.
metricNoOptional sensor metric to filter (for example co2 or temperature).
maximumNoOptional finite inclusive maximum for the selected metric.
minimumNoOptional finite inclusive minimum for the selected metric.
max_pagesNoMaximum pages followed.
page_sizeNoAPI page size.
unlicensedNoInclude unlicensed places.
max_resultsNoMaximum sensor devices returned.
result_offsetNoLocal reading offset; reuse nextResultOffset with identical filters.
response_formatNoText view returned alongside structured content.markdown

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
dataYes
metaNo
summaryYes
Behavior5/5

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

Discloses critical behavior: does not invent safety thresholds, filtering only with metric and bounds. Annotations already declare readOnlyHint and idempotentHint; description adds context beyond annotations.

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?

Description is concise, front-loaded with purpose, then measurements, behavioral note, and return structure. Every sentence adds value, no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given output schema exists and high schema coverage, description covers tool purpose, behavioral constraints, and return components. Adequately complete for a read-only, idempotent tool.

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?

Schema coverage is 100%, so baseline 3. Description adds context about filtering behavior linking metric, minimum, maximum parameters, and lists supported measurements that hint at metric enum values.

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?

Description clearly states it aggregates Spot/Rally Board sensor readings with numeric filters, and lists supported measurements. It distinguishes from sibling tools like occupancy or inventory reports.

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

Usage Guidelines4/5

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

Implies usage for environment sensor data but does not explicitly state when to use this tool vs. alternatives. Sibling tools are listed but no direct comparison or exclusion guidance.

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/bouchecousue/logitech-sync-mcp'

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