Skip to main content
Glama
OpenCyber Harness
by mitkox

oc_technology_hints

Read-onlyIdempotent

Identify deterministic technology hints from supplied HTTP headers and body text to reveal likely server and framework fingerprints for authorized security analysis.

Instructions

Detect deterministic technology hints in supplied HTTP headers and body text.

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

Input Schema

NameRequiredDescriptionDefault
bodyNo
headersNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety and locality profile is covered. The description contributes the meaningful nuance that detection is 'deterministic' (rule-based, not heuristic guessing) and operates only on supplied data, but says nothing about which technology classes are recognized or the limits of detection.

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; the scope restriction ('supplied') and the deterministic qualifier are packed in without wasted words.

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 values need not be explained, and the tool is a simple two-parameter analyzer. Still, an agent gets no information on detection coverage, on whether results include confidence or evidence, or on how to interpret an empty body with populated headers.

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 description coverage is 0%, so the description must carry parameter meaning and it does: it maps the two parameters to HTTP headers and body text respectively, telling the agent what content to supply. It stops short of specifying header key format, case handling, or how the empty-string default for body is treated.

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 and resource ('Detect deterministic technology hints') plus the exact inputs it operates on ('supplied HTTP headers and body text'). It is clearly distinguishable from the offensive-security siblings, though it never names them or states how it differs from a full scanner.

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 when-to-use or when-not-to-use guidance, no prerequisites, and no named alternative. The word 'supplied' weakly implies the caller must already have captured traffic rather than having the tool fetch a URL, but that is inference rather than stated guidance.

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