Skip to main content
Glama

Get Logitech Sync coverage report

logitech_sync_get_coverage_report
Read-onlyIdempotent

Audit contracts, licenses, and warranties for rooms and desks at a specified date. Retrieve sorted coverage rows with expiration status counts.

Instructions

Audit room/desk contracts, licenses, and device warranties at a given date.

    Rows are classified as expired, expiring, active, or unknown expiration. Supply ``as_of``
    for reproducible historical/evaluation queries; otherwise today's UTC date is used. Raw
    epoch timestamps and ISO forms are both retained.

    Returns status counts and chronologically sorted coverage rows. No renewal action occurs.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
as_ofNoPoint-in-time date (YYYY-MM-DD); defaults to today's UTC date.
desksNoInspect desk coverage.
roomsNoInspect room coverage.
max_pagesNoMaximum pages followed.
page_sizeNoAPI page size.
unlicensedNoInclude unlicensed places.
max_resultsNoMaximum coverage rows returned.
result_offsetNoLocal coverage offset; reuse nextResultOffset with identical filters.
response_formatNoText view returned alongside structured content.markdown
expiring_within_daysNoHorizon for classifying coverage as expiring.
include_without_expirationNoInclude licenses/warranties with no returned expiration date.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okNo
dataYes
metaNo
summaryYes
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, etc. Description adds useful context: rows are classified, timestamps retained, sorted, and no renewal action occurs, reinforcing non-destructive behavior.

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?

Front-loaded with purpose, then details. No redundant sentences. Could be slightly more structured but overall concise and 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?

For a report tool with output schema, description covers classification, sorting, and non-action. It doesn't detail all parameters or return structure, but output schema handles that. Adequate given complexity.

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 coverage is 100% with descriptions for all 11 parameters. The description adds minimal extra meaning beyond what schema already provides (e.g., reiterates as_of usage). 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?

First sentence clearly states the resource ('room/desk contracts, licenses, and device warranties') and action ('audit'). The description distinguishes from siblings by focusing on coverage aspects, not inventory, occupancy, or 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 guidance on the as_of parameter for historical queries and notes that no renewal action occurs. However, it does not explicitly compare with sibling tools or state when to use this tool over others.

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