Skip to main content
Glama
WYRE-AI

superops-mcp

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

superops_assets_software

Retrieve software inventory for a specific asset, including name, version, install date, bit version, and install path. Supports search and pagination.

Instructions

Get the software inventory for a specific asset: name, version, install date, bit version and install path.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, 1-based (default: 1, max: 2147483647)
searchNoSubstring of the software name, matched case-insensitively. Matches the name only, not the manufacturer.
assetIdYesThe unique asset ID
pageSizeNoResults per page (default: 50, max: 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.2
    • removedInput schema / properties / max
      Removed value: -{
-  "default": 100,
-  "description": "Maximum number of results (default: 100)",
-  "type": "number"
-}
    • addedInput schema / properties / page
      Added value: +{
+  "default": 1,
+  "description": "Page number, 1-based (default: 1, max: 2147483647)",
+  "type": "number"
+}
    • addedInput schema / properties / pageSize
      Added value: +{
+  "default": 50,
+  "description": "Results per page (default: 50, max: 100)",
+  "type": "number"
+}
    • changedInput schema / properties / search / description
      Previous value: -"Search term to filter software by name"New value: +"Substring of the software name, matched case-insensitively. Matches the name only, not the manufacturer."
  2. Addedv1.6.3
  3. Removedv1.6.0
  4. First observedv1.2.5

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It implies a read-only retrieval and lists the fields returned, which is useful, but it never mentions that results are paginated or that search only matches the software name, nor any permission or rate-limit considerations.

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?

One sentence, front-loaded with the verb and resource, and the field list is packed directly after the colon with zero filler.

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?

With no output schema, the description usefully substitutes by enumerating the returned fields (name, version, install date, bit version, install path). Only the pagination behavior and the scope of the search filter are left unaddressed, and both are covered by the input schema.

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%, with page, search, assetId and pageSize all documented in the schema itself, so the baseline is 3. The description adds no parameter-level detail (e.g., that search is substring/case-insensitive) beyond what the schema already states.

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 names a specific verb ('Get') and resource ('software inventory') and enumerates the returned fields, so the agent knows exactly what the tool fetches. It does not, however, differentiate itself from the nearby superops_assets_patches or superops_assets_get siblings, which have similarly shaped 'for a specific asset' semantics.

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 when-to-use or when-not-to-use guidance and no named alternative. The agent must infer from the word 'software' that this is the sibling to pick over assets_patches; nothing in the text routes it.

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