Skip to main content
Glama

List Logitech Sync places

logitech_sync_list_places
Read-onlyIdempotent

Fetch a paginated list of rooms and desks from Logitech Sync using a continuation cursor. Customize with projection fields and detail level.

Instructions

Fetch one controlled page of rooms/desks using the native continuation cursor.

    Use this primitive when exact API pagination or custom projections matter. It never follows
    the cursor automatically. If an explicit projection requests device info, sensors, or
    warranty while ``detail_level=concise``, the result is transparently promoted to detailed
    output and reports that adjustment. A response that is too large fails with guidance
    instead of silently discarding requested fields or inaccessible items.

    Returns ``places`` and metadata including ``next_continuation`` and the effective
    projection. Errors explain how to fix invalid scopes, projections, credentials, or quotas.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
desksNoInclude desks in this page.
limitNoMaximum places for this single API page.
roomsNoInclude rooms in this page.
projectionNoFields to request. Omit for the API default; pass [] for place ids only. place.device is added automatically for nested device fields. Explicit device info, sensors, or warranty projections automatically promote concise output to detailed so requested fields are never discarded.
unlicensedNoInclude unlicensed places, which only expose basic fields.
continuationNoOpaque cursor returned by a previous call; never decode or edit it.
detail_levelNoconcise selects high-signal fields; detailed preserves API fields. Concise is automatically promoted to detailed when an explicit projection requests device info (including peripherals/full network), sensors, or warranty.concise
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?

Annotations already indicate idempotency, read-only, and non-destructive nature. The description adds that the tool never auto-follows cursors, transparently promotes detail_level for certain projections, and reports large response failures with guidance. No contradictions.

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, well-structured paragraph that front-loads the core purpose and then adds behavioral details. Every sentence provides necessary information without redundancy.

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's complexity (8 parameters, no required fields, output schema present), the description covers pagination, projection behavior, error handling, and response format comprehensively. It is fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, but the description adds significant value by explaining parameter interactions (e.g., projection promotion, detail_level auto-promotion, continuation usage) beyond the schema definitions.

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 'Fetch one controlled page of rooms/desks using the native continuation cursor,' specifying the verb, resource, and mechanism. The title reinforces this, and the tool is distinct from siblings like logitech_sync_search_inventory.

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?

The description advises using this tool when exact API pagination or custom projections matter, and notes it never follows the cursor automatically. It doesn't explicitly state when not to use, but provides sufficient context for selection among siblings.

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