Skip to main content
Glama
sonisoft-cnanda

now-sdk-ext-mcp

Lookup Table Columns

lookup_columns

List or search columns on a ServiceNow table to find field names, types, and metadata. Validate column names and check attributes like mandatory or read-only status.

Instructions

List or search columns (fields) on a ServiceNow table. Queries the sys_dictionary table to find column names, types, and metadata for a given table.

Use this tool to:

  • List all columns on a table to see what fields are available

  • Validate a column name before using it in a query or script

  • Find the correct internal element name when you only know the display label

  • Check column types, whether a field is mandatory, read-only, or a reference

Returns: element name (internal), column label (display), type, max length, reference target, mandatory/read-only/active flags.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
instanceNoThe ServiceNow instance auth alias (e.g., "myinstance", "prod"). If not provided, falls back to the SN_AUTH_ALIAS environment variable.
tableYesThe internal table name to look up columns for (e.g., "incident", "cmdb_ci_server", "sys_user"). Use lookup_table first if you are unsure of the exact table name.
search_termNoOptional filter to search columns by element name or label. Case-insensitive partial matching (contains). Examples: "assigned", "priority", "sys_created". If omitted, returns all columns on the table.
limitNoMaximum number of columns to return. Default is 50, max is 200.
Behavior4/5

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

No annotations provided; description carries full burden. Describes the source (sys_dictionary) and return fields (element name, label, type, etc.). Does not mention potential rate limits or authentication details, but these are implied by the instance parameter. Adequate for a read-only metadata tool.

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?

Concise: one sentence for purpose, bullet list for use cases, then return format. No redundancy. Front-loaded with key information. Every sentence adds value.

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

Completeness5/5

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

Despite no output schema, description thoroughly explains return values (element name, label, type, etc.). Advises on using sibling tool for table name lookup. Covers all necessary context for effective use.

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

Parameters4/5

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

Schema covers 100% of parameters with descriptions. Description adds context beyond schema: explains case-insensitive partial matching for search_term, default/max for limit, and fallback for instance. Also aligns use cases with parameters. Exceeds baseline expectation.

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?

Clearly states 'List or search columns (fields) on a ServiceNow table' and specifies it queries sys_dictionary. Distinguishes from sibling 'lookup_table' by advising to use that tool if unsure of table name. Provides multiple concrete use cases.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly enumerates when to use: list all columns, validate column name, find internal name, check metadata. Provides a when-not-to-use by referencing 'lookup_table' for uncertain table names. No alternative tools mentioned but the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sonisoft-cnanda/now-sdk-ext-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server