Logitech Sync MCP

Overview Schema Related Servers Score Discussions

List Logitech Sync device issues

logitech_sync_list_device_issues

Read-onlyIdempotent

Diagnose offline, unhealthy, stale, or incomplete-peripheral devices by returning issue counts, reason codes, and location details. Provides scan-completeness metadata.

Instructions

Diagnose offline, unhealthy, stale, or incomplete-peripheral devices.

    Each returned device includes explicit reason codes and its containing room/desk. A stale
    cutoff is only applied to Offline devices when the caller provides
    ``last_disconnection_before`` because Logitech defines ``lastSeen`` as the last
    disconnection event, not a heartbeat. Timestamps remain UTC and retain raw epoch values.

    Returns issue counts, reason counts, bounded issue details, and scan-completeness metadata.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`desks`	No	Inspect desk devices.
`rooms`	No	Inspect room devices.
`max_pages`	No	Maximum pages followed.
`page_size`	No	API page size.
`unlicensed`	No	Include unlicensed places.
`max_results`	No	Maximum issue devices returned.
`include_error`	No	Include devices with Error health.
`result_offset`	No	Local issue offset; reuse nextResultOffset with identical filters.
`include_offline`	No	Include Offline devices.
`include_warning`	No	Include devices with Warning health.
`response_format`	No	Text view returned alongside structured content.	markdown
`last_disconnection_before`	No	Optional ISO-8601 cutoff; include Offline devices whose last documented disconnection event occurred before it.
`include_peripheral_mismatches`	No	Include expected/actual camera, speaker, hub, and mic mismatches.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`data`	Yes
`meta`	No
`summary`	Yes

Tool Definition Quality

A4.1/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds valuable context: stale cutoff only applies when last_disconnection_before provided, timestamps are UTC epoch, and explains return content (issue counts, reason codes, etc.).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is concise and front-loaded with main purpose. Every sentence adds meaningful detail without redundancy. Could benefit from better structure (e.g., bullet points for return content), but current form is efficient.

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?

Given 13 parameters and output schema, the description covers key behavioral aspects (stale cutoff, return items) and the tool's scope. Does not explain every health status or filter, but output schema likely covers that. Sufficient for an agent to invoke correctly.

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 parameters are well-described individually. The description adds extra meaning by clarifying the interaction between stale cutoff and last_disconnection_before parameter, which is not evident from schema alone.

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?

Clearly states it diagnoses offline, unhealthy, stale, or incomplete-peripheral devices. Differentiates from sibling tools like list_places or check_connection by focusing on device issues.

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?

Provides context on when to use this tool (diagnosing issues) and explains the last_disconnection_before parameter behavior, but does not explicitly compare with siblings or state when not to use it.

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

Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly
Lightport: Open-Sourcing Glama's AI Gateway
By punkpeye on April 27, 2026.
OpenAI
open source

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