Skip to main content
Glama

fluent_sdk_query

Read-only

Run read-only ServiceNow Table API queries through the SDK CLI with saved credentials to resolve sys_ids, inspect schemas, check records, and read choice values while authoring Fluent code.

Instructions

Run now-sdk query <table>: a read-only Table API query through the ServiceNow SDK CLI using its saved credentials (no browser). Ideal while authoring Fluent code: resolve sys_ids, inspect schemas, check existing records, read choice values. Example: { table: "sys_user_role", query: "name=admin", fields: ["sys_id","name"], limit: 1 }

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": {
      "table": "<table>"
    },
    "name": "fluent_sdk_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
authNonow-sdk credential alias (optional, defaults to the SDK default)
limitNoMax rows per page (default 100)
queryNoEncoded query (e.g., "name=admin^active=true"). Defaults to all records.
tableYesTable to query (e.g., "incident", "sys_dictionary")
fieldsNoFields to return (e.g., ["sys_id","name"])
offsetNoStarting offset for paging
display_valueNoReturn display values, raw values, or both

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv5.0.1
    • addedInput schema / properties / auth
      Added value: +{
      +  "description": "now-sdk credential alias (optional, defaults to the SDK default)",
      +  "type": "string"
      +}
    • addedInput schema / properties / display_value
      Added value: +{
      +  "description": "Return display values, raw values, or both",
      +  "enum": [
      +    "true",
      +    "false",
      +    "all"
      +  ],
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Max rows to return"New value: +"Max rows per page (default 100)"
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Starting offset for paging",
      +  "type": "number"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Encoded query string (e.g., \"name=admin^active=true\")"New value: +"Encoded query (e.g., \"name=admin^active=true\"). Defaults to all records."
  2. Addedv4.9.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered structurally. The description adds genuinely useful context beyond them — the SDK CLI mechanism, saved-credential auth with no browser session, and read-only Table API semantics — but says nothing about result size limits, paging behavior, or failure modes when credentials are missing.

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?

Front-loaded with the mechanism in the first clause, then use cases, then a concrete example. Every sentence carries information and there is no filler or restatement of the schema.

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?

No output schema exists, so the description should ideally hint at what comes back (rows/fields, paging interaction with offset/limit); it only implies this via the example. Otherwise it is sufficient for a 7-parameter read tool whose parameters are fully documented in the schema.

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 description coverage is 100%, so the baseline is 3. The description goes modestly beyond by tying the `table` parameter to the CLI positional and giving a worked JSON example that shows how table/query/fields/limit compose, which helps an agent assemble a correct call.

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 concrete verb+resource ("read-only Table API query") and pins down the exact mechanism ("Run `now-sdk query <table>` ... through the ServiceNow SDK CLI using its saved credentials (no browser)"). This distinguishes it implicitly from browser/natural-language query siblings, though it never names an alternative tool directly.

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?

Gives clear context for when to reach for it: "Ideal while authoring Fluent code: resolve sys_ids, inspect schemas, check existing records, read choice values" — four concrete scenarios. It stops short of exclusions or naming when a sibling (e.g. a saved-credentials-free or natural-language query path) would be preferred.

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