Skip to main content
Glama

fluent_version

Read-only

Checks the installed @servicenow/sdk (now-sdk) version against the NowAIKit target (currently 4.14.2) and returns an upgrade hint when outdated.

Instructions

Report the installed @servicenow/sdk (now-sdk) version and whether it meets the version NowAIKit tracks features against (currently 4.14.2). Returns an upgrade hint when out of date.

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": "fluent_version"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.9.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine context beyond that: the specific version baseline features are tracked against and the conditional upgrade hint. With no output schema, it usefully discloses what comes back, though it doesn't specify the exact return shape (e.g., a version string versus a structured object).

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 compact sentences with the core purpose front-loaded and the conditional upgrade behavior trailing. Every clause carries information: the package name, the alias, the tracked version, and the hint behavior. No filler or repetition of the tool name.

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 zero-parameter, read-only version check with no output schema, the description covers purpose, threshold, and conditional output, which is close to everything an agent needs. The only gap is the precise response format, which matters slightly more here because no output schema exists to define it.

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?

The tool takes zero parameters, so there is no parameter semantics to document; the baseline for a parameterless tool applies. Nothing in the description misleads about inputs, and it correctly implies the call needs no arguments.

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?

The description names a specific verb and resource: it reports the installed `@servicenow/sdk` (now-sdk) version and whether that version meets the tracked target. It also states the concrete threshold (4.14.2) and the upgrade-hint behavior, so an agent can tell this is a version check rather than a build/install operation. It stops short of explicitly distinguishing itself from similarly named siblings such as fluent_sdk_query or fluent_dependencies.

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?

Usage is only implied: an agent can infer this is the tool to call when it needs to know the installed SDK version or whether an upgrade is needed. There is no explicit when-to-use statement, no exclusion of alternatives, and no mention of prerequisites such as whether a project must be initialized first.

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