Skip to main content
Glama
Sign In
HexStrike AI MCP

HexStrike AI MCP

by Lyrie-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

capabilities_describe

Retrieve operation schemas, supported versions, informational risk labels, and usage examples for specified capability IDs to understand available operations and version compatibility.

Instructions

Return operation schemas, supported versions, informational risk labels, and examples. Risk labels do not restrict execution.

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": {
      "capability_ids": "<capability_ids>"
    },
    "name": "capabilities_describe"
  }
}

Input Schema

NameRequiredDescriptionDefault
probe_versionNo
capability_idsYes

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 behavioral burden. It usefully discloses that risk labels are informational and do not restrict execution, but it does not explicitly state that this is a read-only operation, nor does it describe authorization needs or side effects.

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 short sentences with zero waste. The returned artifacts are front-loaded, and the risk-label caveat is placed immediately after.

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 detail is not strictly required, and the risk-label note adds important context. However, the missing parameter explanation and usage guidance leave material gaps for an agent deciding when and how to call 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%, and the description never names or explains capability_ids or probe_version. The mention of operation schemas and versions offers only a weak hint about what capability_ids represent.

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, 'Return', and the artifacts returned: operation schemas, supported versions, risk labels, and examples. It is clear what the tool does, though it does not explicitly distinguish itself from the sibling capabilities_search.

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 guidance, no comparison to capabilities_search or action_prepare, and no prerequisites. Inspection usage is only weakly implied by 'Describe'.

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