ServiceNow_Developer_Panel

Overview Schema Source Related Servers Discussions Admin

request_tables

Read-onlyIdempotent

Fetch multiple ServiceNow tables in one request with per-table queries, fields, and limits, then cache the combined response so query_cache can join them.

Instructions

Fetch several tables in one request, each with its own query, fields and limit. All of them are stored in one cached response, so query_cache can join them. Returns the row count and columns of each table, any warnings and the cache_name. Example arguments: {"instance": "dev", "tables": [{"table": "sys_user_group", "fields": ["sys_id", "name"], "limit": 1000}, {"table": "sys_group_has_role", "query": "role.name=itil", "fields": ["group", "role", "group.name"], "limit": 5000}]}

Input Schema

Name	Required	Description
`tables`	Yes	The tables to fetch, each with its own query, fields and limit. Each table can appear only once: combine conditions with ^OR or IN instead.
`refresh`	No	Skip the local cache and ask the instance again. Leave false to reuse a recent response.
`instance`	Yes	Name of a configured instance, as returned by list_instances.

Output Schema

Name	Required	Description	Default
`source`	Yes
`sections`	Yes
`warnings`	Yes
`row_count`	Yes
`cache_name`	Yes
`elapsed_ms`	Yes
`executed_at`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 4, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare the tool as read-only, idempotent, and open-world. The description adds meaningful behavior beyond those annotations: all tables are stored in one cached response, query_cache can join them, and the result includes row counts, columns, warnings, and cache_name.

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 front-loaded, efficient, and free of wasted wording. The example is directly useful for illustrating the nested table request structure.

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?

Given the rich schema, annotations, and output schema, the description is complete enough for correct invocation. It covers the multi-table caching behavior, the query_cache relationship, and the returned summary, and supplies an example of the argument shape.

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 coverage is 100%, so the schema already documents instance, refresh, and each table's query, fields, and limit. The description reinforces that each table has its own query/fields/limit and provides an example, but it does not add semantic detail beyond the schema.

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 states a specific verb and resource: fetch several tables in one request, each with its own query, fields, and limit. The phrase 'several tables' clearly distinguishes it from the singular sibling request_table.

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?

It gives clear usage context for fetching multiple tables and notes that query_cache can join the cached response. It does not explicitly name request_table or add_tables as alternatives, but the multi-table scope implies the distinction.

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

Deploy Server