openstack-mcp-server

List network agents

list_network_agents

Read-onlyIdempotent

Lists Neutron network agents with host and liveness details, filterable by host, agent type, and project. Use it to check agent availability and required roles before network troubleshooting.

Instructions

List Neutron agents with host and liveness. Usually needs more than a project reader role; forbidden means the role is missing, not that the list is empty. Not paged; narrow with filters.

Input Schema

Name	Required	Description
`host`	No
`limit`	No	Maximum items to return (1-100, default 50).
`agent_type`	No
`project_id`	No	Project ID to work in; omit for the default project. Allowed values are listed by get_scope.

Output Schema

Name	Required	Description
`items`	Yes
`limit`	Yes	Maximum number of items requested.
`complete`	Yes	True when no more items exist beyond this page.
`resource`	Yes	Resource type of the items.
`project_id`	Yes	Project whose session produced the list.
`next_marker`	No	Pass as marker to read the next page; null when complete or when the API has no marker paging.
`observed_at`	Yes	UTC time the list was read.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 30, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses the RBAC prerequisite (usually more than a project reader role), how a 403 should be read (missing role, not an empty result), and that the operation is not paged. Those are exactly the traits that change an agent's behaviour on failure and result-size assumptions.

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?

Three short sentences, each carrying a distinct fact, with the core purpose front-loaded and the auth caveat before the paging note. No 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?

An output schema exists, so return values need no explanation, and the description covers auth, error semantics and paging. The remaining hole is what values host and agent_type accept, which leaves the agent guessing at filter syntax.

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 coverage is 50% – limit and project_id are documented in the schema, but host and agent_type have no descriptions anywhere. The description only gestures at them with 'narrow with filters' and gives no hint about accepted agent_type values, so it does not compensate for the gap.

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?

Specific verb plus resource ('List Neutron agents') with the returned fields named ('host and liveness'). The 'Neutron agents' qualifier implicitly separates it from the compute/volume/identity service listers in the sibling set, so an agent can pick it out without opening the schema.

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?

'Narrow with filters' is the only usage steering, and it neither names which filters nor points at alternatives such as list_compute_services or list_services when the wrong agent family is needed. The forbidden-means-missing-role note is useful but is error interpretation rather than when-to-use guidance.

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