Skip to main content
Glama
WYRE-AI

Slide MCP Server

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

slide_list_devices

Retrieve Slide Box devices, filtering by client and creation date to identify physical or virtual devices.

Instructions

List devices (physical or virtual Slide Boxes), filterable by client and creation date.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of items to return per page. Defaults to 10.
offsetNoStarting index for pagination. Defaults to 0.
sort_byNoField to sort by. Defaults to "hostname".
sort_ascNoSort in ascending order. Defaults to false (descending).
client_idNoFilter devices belonging to a specific client.
created_afterNoFilter results to after a specific creation timestamp (RFC3339 format).
created_beforeNoFilter results to before a specific creation timestamp (RFC3339 format).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. 'List' implies a read-only operation and the filterable-by-client/creation-date behavior is stated, but pagination behavior, default ordering, and output characteristics are not disclosed. For a non-destructive list tool this is adequate but not rich.

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 front-loaded sentence with no wasted words. It states the verb, resource, and key filtering capabilities compactly.

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

Completeness3/5

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

With seven fully documented parameters and a clear resource definition, the tool is mostly self-sufficient, but there is no output schema and no mention of pagination/return conventions. The description also lacks routing context relative to sibling get/list tools, leaving some completeness gaps.

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 description coverage is 100%, so the baseline is 3. The description reinforces the client and creation-date filters, but it does not add meaning beyond the schema's already-detailed parameter descriptions for limit, offset, sorting, and timestamps.

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 names a specific verb ('List'), a concrete resource ('devices (physical or virtual Slide Boxes)'), and the available filter dimensions. This clearly differentiates it from singular get-style siblings like slide_get_device.

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

Usage Guidelines2/5

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

The description gives no guidance about when to use this tool versus alternatives such as slide_get_device or slide_list_agents. It does not state exclusions, prerequisites, or conditions that should route an agent to a sibling tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools