Skip to main content
Glama
WYRE-AI

Alloy Navigator MCP Server

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

alloy_list_objects

Retrieve records from Alloy Navigator classes like Incidents, Work Orders, or Computers. Filter by fields, sort, page, or search text to get targeted object lists for further detail or activity queries.

Instructions

List objects of a given Alloy Navigator object class (e.g. Incidents, Work Orders, Computers, Consumables, SoftwareCatalog, or 'Purchase Order Items' - Alloy Navigator does not publish one exhaustive class list; use the object class names configured in your instance, which typically match the module names shown in the Alloy Navigator client). Supports field selection, sorting, paging, free-text search, and per-field filters. Each returned object's OID chains into alloy_get_object and alloy_get_object_activities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filtersNoOptional field-name/value pairs to filter the result, e.g. {"Priority": "High"}. Each pair is sent as a literal <fieldName>=<value> query parameter, matching Alloy Navigator's own filtering convention.
par_limitNoMaximum number of records to return.
par_fieldsNoComma-separated list of field names to include in the result. Omit to return every field.
par_offsetNoNumber of records to skip, for paging.
objectClassYesThe Alloy Navigator object class to list, e.g. 'Incidents' or 'Computers'.
par_sort_ascNoComma-separated list of field names to sort the result by, ascending.
par_sort_descNoComma-separated list of field names to sort the result by, descending.
par_search_textNoFree-text search string to narrow the returned objects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the safety/behavior burden. It discloses the supported query features and the important caveat that object class names are not exhaustively published, but it doesn't mention default paging limits, return structure, or error behaviors. This is acceptable but not rich beyond what schema already implies.

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?

Two sentences carry a clear operation, examples, a necessary configurability warning, capability list, and downstream integration note. The first sentence is slightly long due to the parenthetical, but every clause earns its place.

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?

Complex tool with 8 parameters and no output schema, yet the description covers the central class-name ambiguity and how results chain into sibling tools. Missing details like pagination defaults, max page size, and expected response shape leave some ambiguity for an agent invoking it without examples.

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 schema fully documents all 8 parameters. The description only summarizes capabilities already present in the schema (filtering, sorting, paging, search) and adds no new parameter-level detail, warranting the baseline.

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

Purpose5/5

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

States the operation verb 'List' and the resource ('objects of a given Alloy Navigator object class') with concrete examples. The chaining sentence also positions it as the entry point that yields OIDs for the sibling get tools, so an agent can distinguish list from fetch/detail actions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description gives clear context for when to use: to enumerate objects by class, with filtering/paging/search. It doesn't explicitly say 'use this instead of alloy_get_object when you need many objects,' but the OID chaining note and sibling set make the intended workflow obvious. No explicit exclusions or alternative conditions, so not a 5.

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