Skip to main content
Glama

audit_topology_security

Audit StarHub topology JSON to detect RFC 1918 Wi-Fi subnet collisions and exposed AI sandbox SSH or database ports before deployment.

Instructions

Audit a StarHub topology JSON for RFC 1918 Wi-Fi subnet collisions and exposed AI sandbox SSH/database ports.

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

Input Schema

NameRequiredDescriptionDefault
topology_jsonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations were supplied, so the description carries the full behavioral burden and does very little with it. It does not say whether the operation is read-only, how findings are reported, how severe issues are classified, or what happens if topology_json is malformed. Only 'audit' weakly signals a non-mutating diagnostic.

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?

A single front-loaded sentence with the resource and the specific checks named. Nothing is padded or redundant.

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

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema, the definition never tells the agent what an audit returns: a list of findings, a pass/fail verdict, severity tiers, or remediation hints. Combined with the unexplained input format, the definition is too thin for the agent to call it correctly and interpret the result.

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?

There is one parameter with 0% schema description coverage, so the description must compensate. It names 'topology JSON' but does not clarify that topology_json is a raw JSON string, what structure it expects, or whether it can be omitted (required count is 0). The most consequential ambiguity about the sole input is left unresolved.

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 uses a specific verb ('Audit') plus a specific resource ('StarHub topology JSON') and enumerates the exact defect classes checked: RFC 1918 Wi-Fi subnet collisions and exposed AI sandbox SSH/database ports. That is far more concrete than a generic 'audit topology'. It does not explicitly name the siblings compile_ai_sandbox_policy or render_quic_mesh_guardrails, so it stops short of a 5.

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?

'Audit' implies a pre-deployment check, but the description gives no explicit when-to-use, when-not-to-use, or prerequisites (e.g. must the topology be generated by StarHub first?). It also never states an alternative for the policy-rendering siblings. The agent must infer the context entirely.

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