OpsChugex LocalOps MCP

Overview Schema Source Related Servers Discussions Admin

Local Groups

local_groups

Read-onlyIdempotent

Retrieve bounded group metadata and Linux group membership to inspect host identity, using a limit to control result size.

Instructions

Return bounded local group metadata and Linux group membership where available.

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

Input Schema

Name	Required	Description	Default
`limit`	No

Output Schema

Name	Required	Description	Default
`groups`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 2, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the 'bounded' qualifier and the 'where available' platform caveat, but says nothing about permissions required to enumerate groups or how suppression/truncation behaves.

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?

One compact sentence with no filler and the resource front-loaded. It is efficient, though it spends words on the 'where available' hedge rather than on the parameter it leaves unexplained.

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 described, and annotations cover the read-only nature. However, for a tool with an undocumented limit parameter and no usage routing among the many sibling inventory tools, the description is only minimally adequate.

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 description coverage is 0%, so the single 'limit' parameter (1-300) is undocumented in both schema and description. 'Bounded' loosely alludes to a size cap but gives no default, no maximum, and no statement of what happens when results exceed the limit; the description does not compensate for the coverage gap.

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 and resource: it returns local group metadata and Linux group membership. This clearly distinguishes it from most siblings, though it never names the closest sibling (local_users) or explicitly contrasts group vs user data.

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 guidance, no prerequisites, and no mention of when to prefer local_groups over local_users or local_admins. The only usable context is the tool name itself.

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