Skip to main content
Glama

Look up NetBox asset

malcolm_netbox_lookup
Read-only

Resolve an IP, device name, or prefix to its NetBox asset (role, site, tenant) to identify whether observed traffic involves a known asset and where it sits.

Instructions

Resolve an IP, device name, or prefix to its NetBox asset (role, site, tenant).

    Use this to tell whether observed traffic involves a known asset and where it
    sits — the fast path for the three common NetBox lookups. For any other NetBox
    endpoint (services, VLANs, interfaces, VMs, contacts) use malcolm_netbox_query;
    to list sites use malcolm_netbox_sites. Pass at least one of ip/device/prefix.
    Returns a JSON object with a summarized section per lookup you supplied; a
    lookup that fails carries its own error key while the others still answer,
    and every one failing is reported as an error rather than as a result.

    NetBox is an optional Malcolm subsystem, so found=false is ambiguous on
    its own: malcolm_service_status carries a netbox readiness key, and that
    key is what separates "this asset is not in the inventory" from "this
    deployment has no inventory".
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipNoIP address to resolve to its NetBox asset, e.g. "192.0.2.77". Empty = skip the IP lookup.
deviceNoDevice name to search for, e.g. "switch-01". Empty = skip the device lookup.
prefixNoNetwork prefix to query, e.g. "192.0.2.0/24". Empty = skip the prefix lookup.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Beyond the annotations (readOnlyHint, openWorldHint, destructiveHint), the description adds substantial behavioral context: per-lookup summary sections, independent error handling per lookup, all-failing results as an error, and the ambiguity of found=false due to NetBox being an optional subsystem with readiness key in malcolm_service_status. No contradictions with annotations.

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?

The description is front-loaded with the primary purpose in the first sentence, followed by usage guidance, return/error behavior, and the NetBox-readiness nuance. Each sentence earns its place; no wasted words, well-structured for readability and decision-making.

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?

The tool has an output schema and the description explains return structure, error semantics, and the critical ambiguity around found=false, referencing malcolm_service_status. Combined with schema and annotations, it is fully self-contained for an agent to select and invoke correctly, including alternatives and prerequisites.

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 descriptions already fully cover the individual parameters with examples (100% coverage), so baseline is 3. The description adds the 'Pass at least one of ip/device/prefix' constraint and clarifies that each supplied parameter becomes a lookup section, enriching the meaning beyond the schema alone.

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?

The description opens with a specific verb and resource: 'Resolve an IP, device name, or prefix to its NetBox asset (role, site, tenant).' It clearly distinguishes from siblings by naming malcolm_netbox_query and malcolm_netbox_sites as alternatives for other endpoints, and characterizing this tool as the 'fast path for the three common NetBox lookups.'

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

Usage Guidelines5/5

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

Explicit guidance on when to use this tool ('to tell whether observed traffic involves a known asset and where it sits') and when to use alternatives ('For any other NetBox endpoint... use malcolm_netbox_query; to list sites use malcolm_netbox_sites'). It also instructs to pass at least one of ip/device/prefix, and references malcolm_service_status for disambiguating found=false.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nagameTW/mcp-server-malcolm'

If you have feedback or need assistance with the MCP directory API, please join our Discord server