Skip to main content
Glama
Sign In
DEX_MCP

DEX_MCP

Official
by teamviewer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

devices_search

Find devices using filters, sorting, and pagination. Optionally include devices from child management groups to broaden your search.

Instructions

Search devices with filter/sort/pagination. Body is a SearchPostModel: start (integer offset), pageSize, sort array. includeInherited=true includes devices from child management groups.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "devices_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoSort specs, e.g. [{"property":"Fqdn","direction":"asc"}]
startNoOffset for pagination
pageSizeNoNumber of results to return
includeInheritedNoInclude devices from child management groups (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It does explain includeInherited behavior and the pagination/sort inputs, and the read-only nature of a search is reasonably implied. However, it does not describe the response shape, pagination defaults, maximum page sizes, or any access requirements.

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?

The description is concise and front-loaded with the main purpose, followed by parameter details and the includeInherited caveat. It is efficient, though the phrase 'Body is a SearchPostModel' is somewhat redundant with the schema and the unsupported 'filter' claim introduces mild ambiguity.

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

Completeness2/5

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

The description is not complete for a search tool with no annotations and no output schema. It leaves the response format and pagination behavior unspecified, offers no comparison to sibling device tools, and claims filter support that is not reflected in the input schema, making it harder for an agent to know exactly what this endpoint returns and how to use it effectively.

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 adds some value by clarifying 'start' as an integer offset and explaining the effect of includeInherited, but it mostly paraphrases the schema's existing parameter descriptions without adding substantial new meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Search'), the resource ('devices'), and the core capabilities (filter/sort/pagination), which distinguishes it from sibling get/list tools like devices_get_by_fqdn and devices_list. It does not explicitly name alternatives, and the mention of 'filter' is slightly misleading because the input schema exposes no filter parameter.

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?

There is no guidance on when to use this tool versus the many sibling device tools such as devices_list, devices_get_by_fqdn, or devices_summary. The description implies a search use case but does not state when not to use it or which alternative to choose for simple listing or direct lookup.

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