Skip to main content
Glama
Sign In
Cybersec Toolkit

Cybersec Toolkit

by 26zl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_profile_tools

Read-onlyIdempotent

List the exact tools a named profile would install, grouped by module with install status, or return counts only to review per-module totals before installing.

Instructions

List every tool that a specific profile would install.

Given a profile name, returns the complete list of tools grouped by module, with install status for each. This lets you see exactly what you get before running the install command.

A full profile lists hundreds of tools; pass counts_only=True for just the per-module counts and totals when the full tool list is not needed.

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": {
      "profile": "<profile>"
    },
    "name": "get_profile_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileYesProfile name (e.g. "ctf", "redteam", "web", "full").
counts_onlyNoIf true, omit the per-tool entries and return only per-module and overall counts.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.0
    • addedInput schema / properties / counts_only
      Added value: +{
+  "default": false,
+  "description": "If true, omit the per-tool entries and return only\nper-module and overall counts.",
+  "type": "boolean"
+}
  2. First observedv1.2.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and a closed-world scope, so the safety profile is covered. The description adds useful operational context the annotations lack: a full profile can list hundreds of tools and the counts_only flag is the mitigation for that cost.

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?

Front-loaded with the core behavior, followed by a return-shape note and a performance tip. Three short paragraphs, no repetition of the schema or annotations, and every sentence carries information.

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

Completeness5/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 needn't be spelled out here. With annotations covering safety and the schema covering both parameters fully, the description supplies the remaining context (grouping, per-tool install status, scale warning) that an agent needs.

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 100%, so baseline is 3. The description goes further by explaining the intent behind counts_only (skip the full tool list when it isn't needed) and by noting results are grouped by module with install status, which helps the agent interpret the output.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('List every tool that a specific profile would install') and makes clear it is scoped to a profile, which separates it from list_tools and list_profiles in the sibling set.

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?

Explains the use case ('see exactly what you get before running the install command') and tells the agent when to switch modes via counts_only=True. It does not explicitly name a sibling alternative or an exclusion case, which keeps it short of a 5.

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