openstack-mcp-server

List projects

list_projects

Read-onlyIdempotent

Lists OpenStack Keystone projects with optional name, domain, and project ID filters to inspect identity resources.

Instructions

List Keystone projects. 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
`name`	No
`limit`	No	Maximum items to return (1-100, default 50).
`domain_id`	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

A3.6/5.0

Behavior4/5

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

With annotations already declaring readOnlyHint=true, idempotentHint=true, and destructiveHint=false, the description adds meaningful behavior: authorization can fail with 'forbidden' even when results would not be empty, and the result set is not paged. It does not describe return shape, but an output schema exists.

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 three short sentences, front-loads the purpose, and uses the remaining space for non-obvious operational guidance. There is no wasted text.

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 read-only list tool with rich annotations and an output schema, the description covers the key non-obvious risks: permissions, 'forbidden' interpretation, and lack of pagination. The main remaining gap is that filter parameters are not explained.

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

Parameters2/5

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

Schema description coverage is only 50%, and the description does not map 'filters' to the actual parameters. The name and domain_id parameters lack schema descriptions, and the description does not explain their semantics or filtering behavior beyond the generic instruction to 'narrow with filters.'

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 opens with a specific verb and resource: 'List Keystone projects.' That is enough to identify it as a project-listing tool, though it does not explicitly differentiate it from project-adjacent siblings such as list_domains or get_scope.

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?

It provides useful operational context: role requirements, the meaning of 'forbidden', that results are not paged, and that filters should be used to narrow results. However, it does not explicitly say when to use this versus alternatives like get_scope or other list tools.

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