Skip to main content
Glama

sn_read

Read one or multiple records from any ServiceNow table using sys_id or an encoded query string. Filter results with fields, limit, and ordering.

Instructions

Read one or many records from any ServiceNow table.

  • Provide sys_id to fetch a single record by ID

  • Provide query (encoded query string) to search multiple records

  • Leave both blank to get the first N records

Examples: table="incident" sys_id="abc123..." table="incident" query="active=true^priority=1^assigned_to=javascript:gs.getUserID()" limit=10 table="sys_user" query="active=true^email=john@company.com" table="sc_cat_item" query="active=true^nameLIKElaptop" fields="name,short_description,price"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tableYesServiceNow table name
sys_idNoFetch a single record by sys_id
queryNoEncoded query string (e.g. "active=true^priority=1")
fieldsNoComma-separated field names to return
limitNoMax records for multi-record reads
order_byNoField to order by (prefix with - for descending, e.g. "-sys_created_on")
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes behavior for different input combinations and includes examples, but lacks details on return format, pagination, error handling, or any side effects. The default limit is mentioned but not bounds or rate limits.

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 well-structured with bullet points and examples. Every sentence adds value, and it is front-loaded with the core purpose. No fluff or repetition.

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?

Given the complexity (6 parameters, no output schema), the description covers all key use cases and parameter interactions. It is missing details on return format and error handling, but is otherwise comprehensive and complete enough for an agent to use correctly.

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 coverage is 100%, baseline 3. The description adds value by explaining the interplay between sys_id, query, and leaving both blank, and includes concrete examples showing how to combine parameters. This goes beyond the schema's individual field descriptions.

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 'Read one or many records from any ServiceNow table' and distinguishes three use cases (single record by sys_id, multiple by query, first N). This differentiates it from sibling tools like sn_create, sn_update, sn_delete, and fetch_sn_records.

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

Usage Guidelines4/5

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

The description provides explicit guidance on when to use each parameter combination (sys_id for single, query for multiple, both blank for first N). It implicitly contrasts with write tools but does not explicitly state when not to use this tool or provide direct alternatives.

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/pinnintisagarSB/ServiceNow-Dev-MCP'

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