Skip to main content
Glama

Get Logitech Sync occupancy report

logitech_sync_get_occupancy_report
Read-onlyIdempotent

Retrieve live room occupancy, capacity, and utilization metrics. Filter rooms by current occupancy or utilization percentage to identify over-capacity or underutilized spaces.

Instructions

Report live room occupancy, known capacity, utilization, and over-capacity state.

    Logitech documents ``seatCount=0`` as unset, so this workflow marks capacity unknown and
    never divides by zero or labels such rooms over capacity. Results are sorted by current
    occupancy and can be filtered with caller-supplied thresholds.

    Returns bounded room rows and aggregate occupancy/capacity metrics. Live values may change.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_pagesNoMaximum pages followed.
page_sizeNoAPI page size.
unlicensedNoInclude unlicensed rooms.
max_resultsNoMaximum room rows returned.
only_occupiedNoReturn only rooms whose current occupancy is above zero.
result_offsetNoLocal room offset; reuse nextResultOffset with identical filters.
response_formatNoText view returned alongside structured content.markdown
minimum_occupancyNoMinimum current people count.
minimum_utilization_percentNoOptional occupancy/seatCount percentage; excludes unknown capacity.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
dataYes
metaNo
summaryYes
Behavior5/5

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

Beyond annotations (readOnly, idempotent), the description discloses key behaviors: handling seatCount=0 to avoid division by zero, sorting by occupancy, filtering with thresholds, and noting live values. This adds significant context.

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 concise (4 sentences) and front-loaded with the core purpose. No redundant text.

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 the tool has 9 parameters and an output schema, the description covers core functionality, edge cases, sorting, filtering, return structure, and live nature. It is sufficiently 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?

With 100% schema coverage, the description adds little parameter-specific meaning beyond mentioning caller-supplied thresholds. 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?

The description clearly states the tool reports live room occupancy, capacity, utilization, and over-capacity state. It distinguishes itself from sibling tools like get_coverage_report by focusing specifically on occupancy metrics.

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?

Usage is implied (when occupancy data is needed), but the description does not explicitly state when to use this tool over siblings or provide prerequisites/exclusions.

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