Skip to main content
Glama

native_commands

Read-only

Discover native command IDs, owning modules, labels, and enabled/checked states by session or module; discovery only, with no arbitrary command execution.

Instructions

Discover native command IDs, owning modules, labels and enabled/checked states. Discovery is NOT verified execution. No arbitrary command execution is exposed.

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": {
      "session": "<session>"
    },
    "name": "native_commands"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
moduleNo
sessionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

With readOnlyHint and destructiveHint=false already declaring the safety profile, the description still adds a meaningful semantic distinction: discovery is not verified execution and no arbitrary command execution is exposed, warning the agent not to assume it can run commands. It omits how results are filtered or bounded, so it is not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, with the capability stated first and the scope caveat immediately after; nothing is padded. The phrasing is terse enough that it borders on under-specification rather than waste.

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?

The description usefully enumerates what a discovered entry contains (IDs, modules, labels, enabled/checked states), which substitutes for the missing output schema. However, for a three-parameter tool with zero schema descriptions, it leaves input semantics and result shape/pagination unexplained.

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 all three parameters (session, query, module), and the description does not explain what session means or how query/module narrow results. 'Owning modules' loosely hints at the module filter, but query and the required session are left entirely to inference.

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 names a specific verb and resource set: 'Discover native command IDs, owning modules, labels and enabled/checked states.' It also explicitly bounds the scope ('Discovery is NOT verified execution'), which separates it from verification/apply siblings, though it never names those siblings directly.

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

Usage Guidelines3/5

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

The statement 'Discovery is NOT verified execution' implies the tool is for enumeration only and that checking or applying belongs elsewhere, but the alternative tools are never named nor is the condition for switching. It is implied usage rather than explicit when/when-not guidance.

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