servicenow-api

Check service qualification

servicenow_check_service_qualification

Creates a technical service qualification request to check if requested services can be delivered based on party, location, and service details.

Instructions

Creates a technical service qualification request.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "relatedParty": "<relatedParty>",
      "serviceQualificationItem": "<serviceQualificationItem>"
    },
    "name": "servicenow_check_service_qualification"
  }
}

Input Schema

Name	Required	Description	Default
`type`	No
`externalId`	No
`description`	No
`relatedParty`	Yes
`serviceQualificationItem`	Yes
`expectedQualificationDate`	No
`effectiveQualificationDate`	No
`checkServiceQualificationDate`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.4.0Oct 19, 2026

TDQS

C2.1/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the write semantics are covered structurally and the description's 'Creates' is consistent with them. The description adds nothing beyond that: no mention of side effects, whether a qualification result is returned synchronously, or what state the request lands in.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no filler, which is structurally clean. But the brevity reads as under-specification rather than disciplined conciseness for a tool of this complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool takes 8 parameters with two required nested arrays, has no output schema, and has essentially no schema descriptions. A one-sentence description is nowhere near sufficient to let an agent construct a valid qualification request.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Eight top-level parameters (type, externalId, description, relatedParty, serviceQualificationItem, and three date fields) have zero description coverage in the schema, and the description supplies no parameter meaning at all. With a deep nested object graph and no compensating text, the agent cannot know what to supply for the required relatedParty and serviceQualificationItem structures.

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

Purpose3/5

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

The description gives a verb and resource ('Creates a technical service qualification request'), which is more than a tautology. However, it never reconciles the 'check' framing in the tool name with the 'create' verb used here, nor does it distinguish this from siblings like servicenow_get_service_qualification or servicenow_process_service_qualification_result. An agent has a rough idea but no differentiation.

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 guidance on when to use this tool versus the clearly related siblings (get_service_qualification, process_service_qualification_result), no prerequisites, and no statement of what happens after the request is created. The agent must infer the entire usage context from the name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server