sylvia-iot-mcp

data_network_uldata_list

Retrieve network uplink data records with filters for device, network, address, and time range, enabling IoT data inspection and monitoring.

Instructions

List network uplink data records.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "unit": "<unit>"
    },
    "name": "data_network_uldata_list"
  }
}

Input Schema

Name	Required	Description
`addr`	No	Filter by network address.
`sort`	No	Sort key:order. Keys: proc, time, network, addr.
`tend`	No	End time in milliseconds since epoch.
`unit`	Yes	Unit ID (required for normal users).
`limit`	No	Max items; 0 for all (default 100).
`device`	No	Filter by device ID.
`offset`	No	Data offset (default 0).
`tfield`	No	Time field for filtering: proc or time. Required when using tstart/tend.
`tstart`	No	Start time in milliseconds since epoch.
`network`	No	Filter by network code.
`profile`	No	Filter by device profile.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List' suggests a read-only operation, but the description does not mention default limits, pagination behavior, time-filtering requirements, or what the returned records contain. For a tool with 11 parameters, this is a meaningful gap.

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 compact and front-loaded, with no filler or redundant words. It conveys the core operation immediately, though it is arguably thinner than ideal for a complex list tool.

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?

Given 11 parameters, no annotations, and no output schema, this one-line description is insufficient for an agent to fully understand the tool's behavior, return shape, filtering options beyond the schema, or pagination semantics. The schema covers parameter meaning, but broader operational context is missing.

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 parameters are already well-documented in the schema and the description adds no additional parameter-level meaning. The baseline of 3 applies because the schema handles the heavy lifting.

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 gives a specific verb ('List') and a specific resource ('network uplink data records'), which clearly separates this from count tools and downlink-data tools in the sibling set. However, it does not explicitly describe the scope of the list, such as whether it returns all records or supports filtering/pagination.

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 about when to use this tool versus alternative list/count tools in the sibling set, such as data_network_dldata_list or data_network_uldata_count. The description implies a list operation but never states when this tool is the right choice or when another sibling would be more appropriate.

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

Deploy Server