List ServiceNow import sets with optional filters for state (loaded, partial, transform_failed, complete) or staging table to audit data loads.
List Import Sets with optional filter by state or staging table
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max records to return (default 25) | |
| query | No | Additional encoded query string | |
| state | No | Filter by state: loaded, partial, transform_failed, complete |
Changes observed during successful MCP inspections.
v1.0.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations include readOnlyHint: true, which already indicates a safe read operation. The description does not contradict this and adds no additional behavioral context such as pagination limits or return format, so the bar is met but not exceeded.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence, front-loaded with the operation, and contains no unnecessary words or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple and the schema covers parameters, but there is no description of return values, pagination, or how it relates to sibling import set tools. Given the absence of an output schema, the description is minimally sufficient but lacks completeness.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with each parameter clearly described. The description adds no extra semantic value and introduces a slight inconsistency by mentioning 'staging table' as a filter option without a corresponding top-level parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb and resource ('List Import Sets') and mentions optional filters, making the purpose clear. However, it mentions filtering by 'staging table' which is not a direct parameter in the schema, causing minor ambiguity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like get_import_set or list_data_sources. The description simply states what it does without any when-to-use or when-not-to-use context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.