Skip to main content
Glama

fluent_validate

Read-only

Validates a Fluent (now-sdk) project without installing it by running a frozen-key build that fails on type errors, unknown properties, stale keys, and sys_id conflicts.

Instructions

Check that a Fluent (now-sdk) project compiles cleanly without installing it: runs now-sdk build --frozenKeys --errorOnConflict, so type errors, unknown properties, stale keys and sys_id conflicts all fail. REQUIRES FLUENT_ENABLED=true.

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_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
directoryNoProject directory (contains package.json). Defaults to the working directory.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv5.0.1
    • changedInput schema / properties / directory / description
      Previous value: -"Project directory (optional, defaults to cwd)"New value: +"Project directory (contains package.json). Defaults to the working directory."
  2. Addedv4.9.0

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, it discloses the exact command and flags executed, the four failure classes that will cause the call to fail (type errors, unknown properties, stale keys, sys_id conflicts), and the required environment flag. One small tension remains unaddressed: a build invocation may write output to disk even though readOnlyHint is true, and the description does not say whether artifacts are left behind, so it is not fully transparent about side effects.

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 sentences: the first front-loads what the tool does and the command it runs, the second gives the prerequisite. No filler, and the failure-mode list is compact within the first sentence.

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 validation tool with no output schema, an agent has what it needs: the command, prerequisites, and the conditions that produce failure. The remaining gap is what success looks like in terms of returned content, which the description leaves unstated.

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?

There is a single optional parameter and schema coverage is 100%, so the schema already defines 'directory' fully, including its default. The description never mentions the parameter, so it adds no meaning beyond the schema; the baseline of 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?

The description states a precise verb and resource ('Check that a Fluent (now-sdk) project compiles cleanly') and adds the differentiator 'without installing it', which implicitly separates it from build/install-style siblings. It does not name an alternative tool the way a top-scoring definition would, so it stops just short of full sibling differentiation.

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?

It makes the intended context clear (validate compilation without doing an install) and states a hard prerequisite, 'REQUIRES FLUENT_ENABLED=true', which the agent needs before calling it. It stops short of explicit when-not-to-use guidance or naming the sibling to use when an actual build/install artifact is wanted.

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