List connection and credential aliases for ServiceNow integrations. Filter by type, name, or limit to locate the alias needed for configuring integrations.
List connection and credential aliases used by integrations
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Filter by type: basic, oauth2, api_key, certificate | |
| limit | No | Max records to return (default 25) | |
| query | No | Search by name |
Changes observed during successful MCP inspections.
v1.0.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds minimal context ('used by integrations') but does not disclose behaviors like pagination, sorting, or result size limits beyond what the schema parameters imply.
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, focused sentence that states the tool's purpose with no unnecessary words. It is front-loaded and immediately clear.
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?
For a simple list operation with well-documented optional parameters and no output schema, the description is adequately complete. It could mention default limit or filtering behavior, but these are already captured in the schema.
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?
The input schema covers all three parameters with descriptions, so schema coverage is 100%. The tool description provides no additional parameter meaning, so a baseline score of 3 is appropriate.
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 the verb 'List' and specifies the resource as 'connection and credential aliases used by integrations', making the tool's purpose explicit and distinct from other list tools. It clearly identifies what is being listed and for what context.
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 explicit guidance is provided on when to use this tool versus alternatives, but the purpose is self-evident for listing credential aliases. There are no obvious sibling tools with the same function, so the description implies usage without exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.