Skip to main content
Glama

os_detect

Identify a target's operating system through TCP/IP stack fingerprinting to guide authorized network audits and host assessments.

Instructions

Guess the target's operating system using TCP/IP stack fingerprinting.

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": {
      "target": "<target>"
    },
    "name": "os_detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does add real signal: 'Guess' honestly flags that results are probabilistic rather than authoritative, and 'TCP/IP stack fingerprinting' tells the agent this is an active network probe against the target. It omits whether the probe is intrusive/detectable, whether it needs privileged access or a reachable host, and how accurate results typically are.

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?

A single front-loaded sentence with no filler, hedging, or redundant restatement of the tool name. Everything present earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value explanation is unnecessary, and for a one-parameter probe the description is close to adequate. What is missing is prerequisite context for an unannotated active network operation and any specification of the target parameter format, which leaves the agent under-informed before invoking it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required parameter 'target', and the description says nothing about it. The agent cannot tell whether the target should be an IP address, hostname, or CIDR range, or whether additional options exist. This is a case where the description needed to compensate for the schema gap and does not.

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 gives a specific verb ('Guess'/detect) and resource ('operating system') plus the mechanism ('TCP/IP stack fingerprinting'), which is enough to distinguish it from audit-style siblings like ssh_audit or http_audit. It stops short of naming or contrasting any specific sibling, so it sits at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use, when-not-to-use, or alternative routing guidance. The agent must infer that this is the right tool for OS identification rather than, say, service_scan, purely from the verb and the word 'fingerprinting'. The implication is clear but no guidance is actually stated.

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