Skip to main content
Glama
mfa-servicenow-mcp

mfa-servicenow-mcp

by jshsakura

manage_scripted_rest

List and retrieve ServiceNow Scripted REST services and resources, enabling quick lookup of sys_ids for sys_ws_definition and sys_ws_operation records.

Instructions

CRUD Scripted REST services + resources (sys_ws_definition/sys_ws_operation). Use list/get to find sys_ids.

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": {
      "action": "<action>"
    },
    "name": "manage_scripted_rest"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoService name search
actionYes
offsetNo
serviceNoService sys_id:<id> or name
count_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.25.8
    • addedInput schema / properties / query / description
      Added value: +"Service name search"
  2. Changed2 schema fields changedv1.24.83
    • removedInput schema / properties / confirm
      Removed value: -{
      -  "enum": [
      -    "approve"
      -  ],
      -  "type": "string"
      -}
    • changedInput schema / required
      Previous value: -[
      -  "action",
      -  "confirm"
      -]New value: +[
      +  "action"
      +]
  3. Addedv1.21.20

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and largely drops it. Beyond the table names it says nothing about whether calls are read-only, what records are returned, how limit/offset paginate, or what count_only does, and the 'CRUD' framing actively misleads about available behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences, front-loaded with the resource and tables, with no filler. The only wasted content is the inaccurate 'CRUD' label, which creates ambiguity rather than length.

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 six-parameter tool with no annotations and no output schema, the description should explain the supported operations and the pagination/lookup parameters. Instead it advertises CRUD the tool cannot perform and leaves most parameters undefined, so an agent cannot reliably call it from this definition alone.

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

Parameters2/5

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

Schema coverage is only 33% across six parameters. The description adds meaning only for the id-lookup flow via 'find sys_ids'; query, service, limit, offset, and count_only are neither explained in the description nor fully documented in the schema, so the gap is not compensated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

It names a specific resource family (Scripted REST services and resources) and the underlying tables (sys_ws_definition/sys_ws_operation), which helps separate it from siblings like manage_script_include. However, the stated scope is 'CRUD' while the action enum only permits 'list' and 'get', so an agent reading the description will overestimate what the tool can do.

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?

'Use list/get to find sys_ids' hints at the intended workflow (look up ids before operating on them), which is genuinely useful. There is no guidance on when to prefer this over sibling tools, no preconditions, and no mention of pagination or how to choose between list and get.

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