Skip to main content
Glama
Sign In
secure-kb

secure-kb

by pavnxet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

detect_stack

Fingerprint a codebase path to identify ranked platforms and recommended profiles for security checks.

Instructions

Fingerprint a codebase path and return ranked platforms + recommended profiles.

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": {
      "path": "<path>"
    },
    "name": "detect_stack"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.9.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden. It implies a read-only scan of a path but never confirms it is non-destructive, says nothing about permissions, cost, or what happens with an invalid path, and gives only a bare sketch of the output.

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?

One front-loaded sentence with zero filler: verb, resource, and output all present. Nothing is wasted.

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?

There is no output schema, so the description owns return-value explanation; 'ranked platforms + recommended profiles' is a helpful but thin sketch. Combined with the total absence of usage guidance, it is only minimally adequate for a one-param entry-point tool.

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 0% and the single parameter has no description, so the description must compensate. 'A codebase path' gives the parameter basic meaning (a filesystem location to scan) but adds no format, relative-vs-absolute, or validation detail.

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 ('Fingerprint') and resource ('a codebase path') plus the output ('ranked platforms + recommended profiles'). This makes it distinguishable from siblings like get_profile or search_checks, though it never explicitly contrasts itself with them.

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?

No indication of when to use this versus get_profile, search_checks, or start_report, and no prerequisites such as required access to the path. The agent must infer the entry-point role from the name alone.

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