Skip to main content
Glama
Sign In
SyncroMSP MCP Server

SyncroMSP MCP Server

by advenimus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

assets_list

List customer assets with filters by ID, type, SNMP status, or search query. Returns paginated results.

Instructions

List customer assets with optional filters. Returns paginated results.

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": "assets_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
queryNoSearch query
customer_idNoFilter by customer ID
snmp_enabledNoFilter by SNMP enabled status
asset_type_idNoFilter by asset type ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description must disclose traits. It mentions 'Returns paginated results', but does not explain pagination mechanics, authentication, rate limits, or side effects. Only one behavioral trait is added.

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?

Two efficient sentences: first states purpose, second mentions pagination. No redundant words, well front-loaded.

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?

For a list tool with 5 optional parameters and no output schema, the description covers basic behavior but lacks details like filter semantics, pagination navigation, or result format. Adequate but not rich.

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 baseline is 3. The description adds no additional meaning beyond 'optional filters' which is already implied by no required parameters.

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 'list' and resource 'customer assets', and mentions optional filters and pagination. It sufficiently distinguishes from sibling tools like assets_get or admin_list_items, though no explicit differentiation.

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?

No guidance on when to use this tool versus other list tools (e.g., admin_list_items) is provided. The description lacks context about appropriate scenarios.

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