Skip to main content
Glama
tedorigawa001

ServiceNow-MCP

by tedorigawa001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

query_records

Read-onlyIdempotent

Query ServiceNow records with filtering, field selection, pagination, and sorting

Instructions

Query ServiceNow records with filtering, field selection, pagination, and sorting

Input Schema

NameRequiredDescriptionDefault
limitNoMax records (default: 10, max: 1000)
queryNoEncoded query string (e.g., "active=true^priority=1")
tableYesTable name (e.g., "incident", "change_request")
fieldsNoComma-separated fields to return
orderByNoField to sort by. Prefix with "-" for descending
display_valueNoReturn human-readable values for reference/choice fields. true = display values only ({display_value, link}); "all" = both raw and display ({value, display_value, link}). Omit for raw sys_id/values.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.15.1
    • addedInput schema / properties / display_value
      Added value: +{
+  "description": "Return human-readable values for reference/choice fields. true = display values only ({display_value, link}); \"all\" = both raw and display ({value, display_value, link}). Omit for raw sys_id/values.",
+  "oneOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "enum": [
+        "all"
+      ],
+      "type": "string"
+    }
+  ]
+}
  2. First observedv1.0.2

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds the capability surface (filtering, fields, pagination, sorting) but does not disclose additional behavioral context such as permissions, rate limits, or return format. There is no contradiction with annotations.

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?

The description is a single front-loaded sentence that enumerates the core operations without filler. Every phrase maps to a supported capability, and nothing is wasted.

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?

For a generic multi-table query tool with no output schema and many overlapping siblings, the description covers basic capability but omits return-value shape and selection guidance. Rich annotations and a fully documented schema compensate somewhat, but the definition is not fully complete for confident tool selection.

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 already documents all six parameters in detail. The description maps its broad capabilities to those parameters but adds no syntax or format guidance beyond what the schema provides, making the baseline 3 appropriate.

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 states a specific verb ('Query') and resource ('ServiceNow records') and enumerates filtering, field selection, pagination, and sorting. It is clear what the tool does, but it does not distinguish itself from overlapping siblings such as smart_query, nlq_query, or get_record.

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?

The description names capabilities but gives no explicit when-to-use guidance, exclusions, or alternatives. With many query/search siblings present, an agent is left to infer whether this is the right generic query tool.

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