Skip to main content
Glama
WYRE-AI

gorelo-mcp

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

gorelo_list_assets

Read-only

List managed device assets for a service provider using cursor pagination, keyword/client/status filters, and date ranges; results are sorted newest first.

Instructions

Lists agent (managed device) assets for the service provider using cursor pagination. Results are sorted by createdOn descending (newest first).

Input Schema

NameRequiredDescriptionDefault
queryNoKeyword matched against the device name, display name and description. Up to 200 characters.
cursorNoOpaque pagination cursor from a previous page; omit for the first page.
pageSizeNoNumber of items per page. Clamped to 1–200 (default 50).
clientIdsNoclient ids to include. Omit for every client.
statusIdsNodevice status ids to include: 1 Unreachable, 2 Active, 3 Inactive, 4 Pending Delete, 6 Pending client inactive.
createdSinceNoISO-8601 timestamp; keeps only devices created at or after it.
updatedSinceNoISO-8601 timestamp; keeps only devices updated at or after it.
createdBeforeNoISO-8601 timestamp; keeps only devices created strictly before it.
updatedBeforeNoISO-8601 timestamp; keeps only devices updated strictly before it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv1.1.1
    • addedInput schema / properties / clientIds / description
      Added value: +"client ids to include. Omit for every client."
    • changedInput schema / properties / clientIds / items / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / createdBefore / description
      Previous value: -"ISO-8601 timestamp."New value: +"ISO-8601 timestamp; keeps only devices created strictly before it."
    • changedInput schema / properties / createdSince / description
      Previous value: -"ISO-8601 timestamp."New value: +"ISO-8601 timestamp; keeps only devices created at or after it."
    • changedInput schema / properties / pageSize / description
      Previous value: -"Items per page, clamped 1-200 (default 50)."New value: +"Number of items per page. Clamped to 1–200 (default 50)."
    • changedInput schema / properties / pageSize / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / query / description
      Added value: +"Keyword matched against the device name, display name and description. Up to 200 characters."
    • addedInput schema / properties / statusIds / description
      Added value: +"device status ids to include: 1 Unreachable, 2 Active, 3 Inactive, 4 Pending Delete, 6 Pending client inactive."
    • changedInput schema / properties / statusIds / items / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / updatedBefore / description
      Previous value: -"ISO-8601 timestamp."New value: +"ISO-8601 timestamp; keeps only devices updated strictly before it."
    • changedInput schema / properties / updatedSince / description
      Previous value: -"ISO-8601 timestamp."New value: +"ISO-8601 timestamp; keeps only devices updated at or after it."
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. The description adds genuinely new behavioral facts: results are cursor-paginated and ordered by createdOn descending, which tells the agent how to iterate and what the first page means.

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 sentences, both load-bearing: the first states the resource and pagination model, the second states sort order. Front-loaded and free of repetition of the schema.

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 nine-parameter, fully documented list tool with a read-only hint and no output schema, the description covers the essentials of how to page and what ordering to expect. The only gap is that, absent an output schema, it never indicates what a returned asset record contains.

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% across all nine optional parameters, including the cursor/pageSize mechanics that the description only alludes to. The description adds no filter semantics (e.g., how query matches, whether date bounds compose) beyond what the schema already documents, so baseline 3 applies.

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?

Names a specific verb and resource and narrows the scope to 'agent (managed device) assets for the service provider', which implicitly separates it from the custom-asset siblings in the toolset. It does not name the closest alternative (gorelo_list_custom_assets) explicitly, so an agent must infer the boundary.

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?

Usage is only implied: the description tells you the tool enumerates devices page by page, newest first, with no statement of when to prefer it over gorelo_list_custom_assets or gorelo_get_asset. No prerequisites, exclusions, or alternative routing are given.

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