Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Routers

get_routers

Get list of routers with their configuration.

Instructions

Get list of routers with their configuration.

Functions:

  • Query routers and their external gateway configurations

  • Display router interfaces and connected networks

  • Show routing table entries and static routes

  • Provide comprehensive network routing information

Use when user requests router information, network connectivity queries, or routing configuration.

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

Input Schema

NameRequiredDescriptionDefault
all_projectsNoIf True, list every router Neutron shows the credential in any project (like 'openstack router list' as an administrator). Requires ALLOW_CROSS_PROJECT_READ=true on the server. Neutron returns only what the credential may see, so check scope.warning.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.9.2
    • addedInput schema / properties / all_projects
      Added value: +{
      +  "default": false,
      +  "description": "If True, list every router Neutron shows the credential\nin any project (like 'openstack router list' as an administrator).\nRequires ALLOW_CROSS_PROJECT_READ=true on the server. Neutron\nreturns only what the credential may see, so check scope.warning.",
      +  "type": "boolean"
      +}
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. The verb "Get" and the word "list" make the read-only, non-destructive nature inferable, and the bullets describe what data is surfaced, but nothing is said about cross-project read permissions, the ALLOW_CROSS_PROJECT_READ server flag, scope warnings, or result volume/pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is front-loaded and useful, but the four-bullet "Functions" block is partly redundant: "Display router interfaces and connected networks" and "Provide comprehensive network routing information" overlap heavily, and the final generic bullet adds little. It is readable but padded relative to its informational content.

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?

Return values do not need explaining because an output schema exists, and the single optional parameter is documented in the schema, so the remaining burden is small. The description covers what the tool retrieves and roughly when to reach for it, leaving only cross-project permission behavior undisclosed.

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?

There is a single optional parameter with 100% schema description coverage, so the schema fully explains all_projects, its default, and its server-side dependency. The description adds no meaning beyond that and does not mention project scoping at all, so it neither compensates nor misleads — baseline applies.

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 first line gives a specific verb and resource ("Get list of routers with their configuration"), and the bullet list specifies the sub-content returned: external gateways, interfaces, connected networks, routing table entries, and static routes. It is clearly distinguishable from the identity, image, and load-balancer siblings by resource alone, though it never names an alternative.

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?

"Use when user requests router information, network connectivity queries, or routing configuration" gives a usable trigger context, but there are no exclusions, no prerequisites, and no pointer to any alternative tool for narrower queries (e.g. per-interface or per-network lookups). Usage is implied rather than disambiguated.

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