Skip to main content
Glama
itunified-io

mcp-opnsense

by itunified-io

opnsense_kea_subnet_get

Retrieve the full configuration of a Kea DHCPv4 subnet using its UUID for detailed inspection and troubleshooting.

Instructions

Get detailed configuration of a specific Kea DHCPv4 subnet by UUID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uuidYesSubnet UUID

Implementation Reference

  • The handler case for 'opnsense_kea_subnet_get' in the switch statement. It parses args with a Zod schema requiring a UUID, then calls keaGetSubnet().
    case "opnsense_kea_subnet_get": {
      const { uuid } = z.object({ uuid: UuidSchema }).parse(args);
      return await keaGetSubnet(client, uuid);
    }
  • The keaGetSubnet() helper function that performs the actual API call to OPNsense's Kea endpoint /kea/dhcpv4/get_subnet/{uuid}.
    async function keaGetSubnet(
      client: OPNsenseClient,
      uuid: string,
    ): Promise<{ content: Array<{ type: "text"; text: string }> }> {
      const result = await client.get(`/kea/dhcpv4/get_subnet/${uuid}`);
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • Tool definition registration for 'opnsense_kea_subnet_get' in the dhcpToolDefinitions array. Includes name, description, and inputSchema (requiring a UUID string).
    {
      name: "opnsense_kea_subnet_get",
      description: "Get detailed configuration of a specific Kea DHCPv4 subnet by UUID.",
      inputSchema: {
        type: "object" as const,
        properties: {
          uuid: { type: "string", description: "Subnet UUID" },
        },
        required: ["uuid"],
      },
    },
  • The UuidSchema Zod validation used to validate the uuid argument for the tool.
    export const UuidSchema = z
      .string()
      .uuid("Invalid UUID format");
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states it is a read operation ('Get detailed configuration'), but offers no details on error handling, permissions required, or what happens if the UUID does not exist. The description lacks transparency beyond its basic function.

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 a single sentence with 11 words, directly stating the action and method. It is front-loaded and every word contributes to the meaning. No redundancy or filler.

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

Completeness4/5

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

For a simple get operation with one parameter and no output schema, the description provides essential information: what the tool does and how to identify the target. It does not specify the return format or error handling, but given the simplicity, it is reasonably complete. The context signals indicate no nested objects or enums, so additional detail is less critical.

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 100% (the 'uuid' parameter is described as 'Subnet UUID'). The description adds minimal value by restating that it is identified 'by UUID'. Since the schema already explains the parameter, the description does not significantly enhance understanding.

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 clearly states the action ('Get detailed configuration'), the target resource ('Kea DHCPv4 subnet'), and the identifier method ('by UUID'). It effectively distinguishes from sibling tools like opnsense_kea_subnet_list (which lists multiple subnets) and opnsense_kea_subnet_create (which creates). The verb-resource combination is specific and unambiguous.

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 description implies usage when you have a UUID and need detailed config, but it does not explicitly state when to use this tool versus alternatives like opnsense_kea_subnet_list or opnsense_kea_subnet_get for other versions. No exclusions or prerequisites are mentioned, so guidance is only implied by context.

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/itunified-io/mcp-opnsense'

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