Skip to main content
Glama
modesty

Fluent MCP Server

by modesty

query_fluent_records

Read-only

Run a read-only query against any ServiceNow table using an encoded query string and get matching records as JSON. Configure fields, limits, and pagination for targeted results.

Instructions

Run a read-only query against a ServiceNow table via the Table REST API (SDK v4.8.0+). Returns matching records as a JSON envelope. Requires instance authentication (auto-injected from session, or pass auth explicitly). Provide table and an encoded query (e.g. "active=true^priority<=2").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
authNoCredential alias to use for authentication with instance (auto-injected from session if not provided)
viewNoUI view to determine which fields to return (sysparm_view)
debugNoPrint debug output
limitNoMaximum records per page (sysparm_limit). Default 100.
queryYesEncoded query string (sysparm_query), e.g. "active=true^priority<=2"
tableYesServiceNow table name to query (e.g. incident, sys_user)
fieldsNoComma-separated list of fields to return (sysparm_fields), e.g. "number,short_description,priority"
offsetNoStarting offset (sysparm_offset). Default 0.
selectNoDot/bracket path to extract from the output (SDK v4.10.0+), e.g. "records[0].sys_id". Implies machine-readable output; an unresolved path yields null rather than an error.
noCountNoSkip total count calculation for better performance (sysparm_no_count)
timeoutNoPer-request timeout in milliseconds for each page fetch. Default 30000.
displayValueNoReturn display values (sysparm_display_value): "true", "false", or "all" for both. Default "false".
queryCategoryNoQuery category for extended queries (sysparm_query_category)
queryNoDomainNoIgnore domain separation when querying (sysparm_query_no_domain)
workingDirectoryNoAbsolute path to the Fluent project for this call. Overrides the initialized session and FLUENT_MCP_WORKING_DIR.
excludeReferenceLinkNoExclude reference link metadata (sysparm_exclude_reference_link). Default true.
Install Server

TDQS

A4.4/5.0
Behavior4/5

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

Discloses read-only nature (reinforcing readOnlyHint), mentions authentication requirements, and adds extra behavior like 'unresolved path yields null rather than an error' in the select parameter. No contradiction with annotations; adds context beyond them.

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?

Description is a single, well-structured paragraph that front-loads the core purpose, includes authentication note, and provides an example—every sentence adds value without fluff or repetition.

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?

For a tool with 16 parameters and a fully described schema, the description covers the essential usage pattern and return format. It doesn't explain pagination, but that's not critical given schema coverage and the mention of JSON envelope. Adequate for the complexity.

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 has 100% description coverage (baseline 3). Description adds value by providing a concrete query example and noting SDK version constraints for the select parameter. This enriches parameter meaning 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?

Description clearly states the action (run a read-only query), the target (ServiceNow table via Table REST API), and the outcome (returns matching records as JSON envelope). It also distinguishes this tool as the query capability among siblings, which are all build/deploy/init operations.

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?

Provides clear usage context: requires instance authentication (with auto-injection or explicit auth), and gives an example query. No explicit exclusion or alternative mention, but no alternative query tool exists among siblings, so this is adequate.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/modesty/fluent-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server