Skip to main content
Glama
mfa-servicenow-mcp

mfa-servicenow-mcp

by jshsakura

get_page

Retrieve or list ServiceNow portal pages by URL path, title, or sys_id and return layout tree with widget placements.

Instructions

Get or list portal pages by URL path, title, or sys_id. Returns layout tree with widget placements.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoFilter by title (LIKE match) in list mode
offsetNo
page_idNosys_id or URL path (id). Set → page detail+layout; omit → list pages.
include_layoutNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.25.8
    • addedInput schema / properties / query / description
      Added value: +"Filter by title (LIKE match) in list mode"
  2. Addedv1.22.7
  3. Removedv1.22.0
  4. Addedv1.21.21
  5. Removedv1.21.20
  6. First observedv1.18.41

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral burden. It usefully discloses the return shape ('layout tree with widget placements'), but says nothing about read-only guarantees, pagination behavior for list mode, or the effect of include_layout=false.

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 short sentences with the action and return value front-loaded. No filler or redundant restatement of the name.

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

Completeness2/5

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

For a 5-parameter tool with no annotations and no output schema, the description is too thin: it omits pagination (limit/offset), the include_layout toggle, and the list-vs-detail switch that the schema only hints at. An agent could call it, but not confidently.

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 description coverage is only 40%, and the description adds some meaning by tying page_id/query to URL path, title, and sys_id lookups. It leaves limit, offset, and include_layout entirely undocumented in prose, so it only partially compensates for the coverage gap.

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?

Names a specific verb and resource ('Get or list portal pages') and identifies the lookup keys (URL path, title, sys_id). The dual read/list mode is apparent, though the description doesn't differentiate this tool from nearby siblings like trace_portal_route_targets or get_portal_component_code.

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 'get or list' framing implies two modes, and the schema clarifies that setting page_id triggers detail mode. However, the description itself gives no explicit when-to-use vs. when-to-use-a-sibling guidance, so an agent must infer usage from the schema.

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