Skip to main content
Glama
Sign In
phpIPAM MCP Server

phpIPAM MCP Server

by greglg45
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_vrfs

Retrieve VRF instances from phpIPAM. Optionally set a limit to control the number of results returned.

Instructions

List VRF instances from phpIPAM.

CONTEXT OPTIMIZATION: Limited to 20 results by default.

Args: limit: Maximum number of VRFs to return (default: 20, max: 100)

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the default result limit (20) and max (100), which is useful. However, it omits other behavioral details like ordering or side effects, though the output schema covers return structure.

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 concise and well-structured: a clear purpose statement, a brief context note, and a formatted args section. Every sentence contributes value and the length is appropriate.

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 list tool with an output schema, the description covers the essential aspects: what it lists, the limit behavior, and parameter semantics. It lacks usage guidance, but this is a minor gap for such a straightforward operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but the description fully compensates by explaining 'limit' as the maximum number of VRFs to return, with default and max values. This adds clear meaning beyond the schema's type and default.

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 clearly states 'List VRF instances from phpIPAM,' which is a specific verb and resource. It distinguishes from sibling list tools by the unique resource type (VRFs), though it doesn't explicitly compare with them.

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?

No explicit guidance is given about when to use this tool vs. alternatives. Usage is implied by the tool's name and list context, but there are no exclusions or alternative suggestions, making it adequate but not exceptional.

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

Deploy Server

Other Tools