Skip to main content
Glama
MCP-OpenStack-Ops

MCP-OpenStack-Ops

by call518

Get Project Details

get_project_details

Get OpenStack project details (similar to 'openstack project list/show').

Instructions

Get OpenStack project details (similar to 'openstack project list/show').

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_project_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
all_projectsNoIf True, return a summary (id, name, domain, enabled) of every project the credential's Keystone policy allows (like 'openstack project list'). With a project_name or ID that matches exactly one project, return that project's details and resource counts instead, even for another project; a name shared by several projects returns their summaries, so retry with the ID. Requires ALLOW_CROSS_PROJECT_READ=true on the server; a disabled or denied request is reported as a failure.
project_nameNoName of specific project to show details for (optional). Without all_projects only the current project is available.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.9.2
    • changedInput schema / properties / all_projects / description
      Previous value: -"If True, return a summary (id, name, domain, enabled) of\nevery project the credential's Keystone policy allows (like\n'openstack project list'), optionally filtered by project_name.\nUse get_instance_details or get_volume_list with all_projects for\ntheir resources. Requires ALLOW_CROSS_PROJECT_READ=true on the\nserver; a disabled or denied request is reported as a failure."New value: +"If True, return a summary (id, name, domain, enabled) of\nevery project the credential's Keystone policy allows (like\n'openstack project list'). With a project_name or ID that matches\nexactly one project, return that project's details and resource\ncounts instead, even for another project; a name shared by several\nprojects returns their summaries, so retry with the ID. Requires\nALLOW_CROSS_PROJECT_READ=true on the server; a disabled or denied\nrequest is reported as a failure."
  2. Changed2 schema fields changedv3.8.7
    • addedInput schema / properties / all_projects
      Added value: +{
      +  "default": false,
      +  "description": "If True, return a summary (id, name, domain, enabled) of\nevery project the credential's Keystone policy allows (like\n'openstack project list'), optionally filtered by project_name.\nUse get_instance_details or get_volume_list with all_projects for\ntheir resources. Requires ALLOW_CROSS_PROJECT_READ=true on the\nserver; a disabled or denied request is reported as a failure.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / project_name / description
      Previous value: -"Name of specific project to show details for (optional, lists all if empty)"New value: +"Name of specific project to show details for (optional).\nWithout all_projects only the current project is available."
  3. Changed1 schema field changedv3.5.8
    • addedInput schema / properties / project_name / description
      Added value: +"Name of specific project to show details for (optional, lists all if empty)"
  4. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention permission requirements, cross-project read restrictions, failure behavior, or what happens when a project name is ambiguous. The schema covers some of this, but the description adds almost no behavioral context beyond the CLI analogy.

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

Conciseness4/5

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

The description is a single, front-loaded sentence with no wasted words. It is appropriately concise, though its brevity contributes to gaps in usage and behavioral guidance.

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

Completeness3/5

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

The tool has a rich input schema and an output schema, which reduces what the description must explain. However, with no annotations and no usage guidance, the description is thin for a tool that supports cross-project reads and ambiguous-name handling. It is minimally adequate but not complete.

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%, so the input schema already documents both parameters thoroughly. The description adds no parameter-specific meaning beyond what the schema provides, which is the baseline expectation when schema coverage is high.

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 states a specific verb and resource: 'Get OpenStack project details.' It also anchors the behavior to familiar CLI commands ('openstack project list/show'), making the tool's scope clear. It does not explicitly differentiate from sibling tools, but the purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. The schema contains usage details for all_projects and project_name, but the description itself leaves the agent to infer when each mode applies.

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