Skip to main content
Glama
servicenow-mcp

servicenow-mcp

sn_table_schema

Read-only

Lists a ServiceNow table's columns from sys_dictionary, including name, label, type, max length, mandatory status, and reference target, so you can inspect schema details.

Instructions

List the columns defined on a ServiceNow table, read from sys_dictionary: column name, label, type, max length, whether it is mandatory, and the table a reference points to. Columns inherited from a parent table (for example task for incident) are listed under the parent table name.

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": {
      "table": "<table>"
    },
    "name": "sn_table_schema"
  }
}

Input Schema

NameRequiredDescriptionDefault
tableYesTable name, lowercase letters, digits and underscores only. Example: incident.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already mark it read-only; the description adds useful behavior by naming sys_dictionary as the source and explaining that inherited columns appear under the parent table. It does not cover error cases, permissions, or pagination, but it exceeds annotation-level disclosure.

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?

Two sentences, front-loaded with the action and followed by the important inheritance caveat. The field list is dense but every item is relevant, with no filler.

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?

For a one-parameter read-only schema lookup, the description supplies purpose, source, return attributes, and inheritance behavior. It omits edge-case behavior for missing tables or large results, but with annotations and schema coverage it is largely complete.

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?

There is a single table parameter and schema description coverage is 100%, including allowed characters and an example. The description does not add syntax or format details beyond the schema, so baseline 3 applies.

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 gives a specific verb ('List') and resource ('columns defined on a ServiceNow table'), plus the source sys_dictionary and returned fields. It is clear what the tool does, though it does not explicitly contrast itself with siblings such as sn_table_get or sn_table_query.

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?

It does not state when to use this tool instead of alternatives, nor any when-not conditions. The purpose implies it is for inspecting table schema, but the definition leaves the agent to infer that from context.

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