Skip to main content
Glama
Sign In

Fixlane

by io.github.lightsmite
OverviewDiscussionsAdmin

Check installed software against fixed versions

check_inventory
Read-only

Compares installed programs and versions (at most 50 items, version optional) with verified fixed versions. Each item is affected (below a verified fixed version, with the incident id), not_affected (at or above it) or unknown (no version, an unparsable version, or no verified fixed version for that program and version line).

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": {
      "items": "<items>"
    },
    "name": "check_inventory"
  }
}

Input Schema

NameRequiredDescriptionDefault
osNoThe user's operating system.
itemsYesInstalled programs and versions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: the three-way affected/not_affected/unknown classification, the exact boundary rules for each, and the fact that affected results carry an incident id.

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 with no filler. The core comparison is front-loaded, followed by a tightly packed clause that defines each possible outcome; every clause carries semantic weight.

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 two-parameter read-only tool with full schema coverage and no output schema, the description is nearly complete: it explains input limits, optionality, and the meaning of every possible result value. The one gap is the absence of any signal distinguishing it from the similarly named sibling check_software.

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 coverage is 100%, so both parameters and the nested Item fields are already documented. The description restates the maxItems=50 cap and that version is optional, and links a missing or unparsable version to the 'unknown' outcome, which is a small but real addition beyond the schema.

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 and resource: compares installed programs and versions against verified fixed versions. It is a clear, self-contained purpose, but it never names or distinguishes itself from the close sibling check_software, so an agent must infer which one to call.

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 by the purpose statement; there is no explicit when-to-use, when-not-to-use, or alternative routing (e.g., versus check_software). The 50-item and optional-version constraints hint at how to call it but not when to prefer it.

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

All Fixlane toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources