Skip to main content
Glama

configure_workspace_list

Idempotent

Add or update a list view in a ServiceNow agent workspace by defining its table, title, columns, query filter, category, and order.

Instructions

Add or update a list view in an agent workspace. [Write]

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": {
      "workspace_sys_id": "<workspace_sys_id>",
      "table": "<table>",
      "title": "<title>"
    },
    "name": "configure_workspace_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderNoList order (default 100)
queryNoEncoded query filter (stored in the list condition)
tableYesList table
titleYesList title
columnsNoComma-separated field names
categoryNoList category sys_id or title (default: the workspace's first category, created if none)
workspace_sys_idYesWorkspace sys_id (sys_aw_master_config)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv5.0.1
    • addedInput schema / properties / category
      Added value: +{
      +  "description": "List category sys_id or title (default: the workspace's first category, created if none)",
      +  "type": "string"
      +}
    • addedInput schema / properties / order
      Added value: +{
      +  "description": "List order (default 100)",
      +  "type": "number"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Encoded query filter"New value: +"Encoded query filter (stored in the list condition)"
    • changedInput schema / properties / workspace_sys_id / description
      Previous value: -"Workspace sys_id"New value: +"Workspace sys_id (sys_aw_master_config)"
  2. First observedv1.0.2

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the '[Write]' tag merely repeats structured data. The description adds nothing beyond that: it does not say whether an update overwrites existing list settings, what happens on conflicting titles, or what permission scope is required for openWorld access.

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 short fragments, front-loaded with the action and resource, with no filler prose. The '[Write]' suffix is redundant given the annotations and is the only wasted token.

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

Completeness3/5

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

All 7 parameters are documented in the schema and annotations cover the safety profile, so the definition is minimally sufficient to call the tool. However, for a 7-parameter mutation tool with no output schema, the description gives no indication of what is returned (e.g. created list sys_id) or how add-vs-update is resolved, leaving real gaps.

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 100% across all 7 parameters, including defaults for order and category, so the schema carries the semantic load. The description contributes no additional meaning about parameter interaction, such as whether columns and query are replaced or merged on update; baseline 3 applies.

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?

States a specific verb pair (add or update) and a specific resource (a list view in an agent workspace), which an agent can act on directly. It does not explicitly differentiate itself from siblings such as configure_offline_sync or the many list_* readers, but the verb+object combination is unambiguous enough.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus other configuration tools, no prerequisites (e.g. workspace must exist), and no exclusions. The only cue is the inline '[Write]' marker, which signals mutation but not selection criteria.

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

Deploy Server

Other Tools