Skip to main content
Glama
jschuller

ServiceNow MCP Server

by jschuller
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Get Table Schema

get_table_schema
Read-onlyIdempotent

Retrieve field definitions and data dictionary for a ServiceNow table, with optional inherited fields.

Instructions

Get the data dictionary (field definitions) for a ServiceNow table, including inherited fields

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of fields to return (own fields first, then inherited)
table_nameYesThe table name to get schema for
include_inheritedNoInclude fields inherited from parent tables (e.g. task fields on incident)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.7.0
    • addedInput schema / properties / include_inherited
      Added value: +{
+  "default": true,
+  "description": "Include fields inherited from parent tables (e.g. task fields on incident)",
+  "type": "boolean"
+}
    • changedInput schema / properties / limit / default
      Previous value: -50New value: +200
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of fields to return"New value: +"Maximum number of fields to return (own fields first, then inherited)"
    • changedInput schema / properties / limit / maximum
      Previous value: -500New value: +1000
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "type": "object"
-}New value: +null
  2. First observedv0.5.1

TDQS

A4.3/5.0
Behavior4/5

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

The annotations (readOnlyHint: true, idempotentHint: true, destructiveHint: false) already disclose that this is a safe, read-only operation. The description adds behavioral context by specifying that inherited fields are included in the result, going slightly beyond the annotation coverage.

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, concise sentence that immediately states the core purpose. It avoids unnecessary wording, includes the key qualifier (including inherited fields), and follows a clear structure without any redundancy or tangential information.

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

Completeness4/5

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

The description indicates the output type (data dictionary / field definitions) but does not specify the exact structure or format of the returned data (e.g., list, object). Given that no output schema is provided, this slight gap is acceptable for a simple read-only operation, but a more explicit return format would improve completeness.

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

Parameters5/5

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

All three parameters have descriptive comments in the schema, fully covering their semantics. The limit parameter even explains ordering (own fields first, then inherited), and include_inherited is clarified with an example ('e.g. task fields on incident'). Schema coverage is 100%, and the descriptions are meaningful and unambiguous.

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?

The description clearly states the tool's function: retrieving the data dictionary (field definitions) for a ServiceNow table. It uses a specific verb ('get') and a specific resource ('data dictionary'), and explicitly notes that inherited fields are included, which distinguishes it from record-fetching tools like 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 Guidelines3/5

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

The description does not explicitly mention when to use this tool versus alternatives, but the purpose is sufficiently distinct from sibling tools (such as get_record or list_records) that usage can be inferred. It lacks explicit conditional guidance like 'use this instead of X when…', so it falls short of the highest standard.

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