Skip to main content
Glama

liara_get_bucket

Retrieve configuration and status details for a specific object storage bucket on the Liara cloud platform.

Instructions

Get details of a specific bucket

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesThe name of the bucket

Implementation Reference

  • The main handler function that implements the logic to retrieve details of a specific Liara object storage bucket by its name using the Liara API client. This matches the expected 'liara_get_bucket' tool functionality.
    export async function getBucket(
        client: LiaraClient,
        name: string
    ): Promise<Bucket> {
        validateRequired(name, 'Bucket name');
        return await client.get<Bucket>(`/v1/buckets/${name}`);
    }
  • TypeScript interface defining the structure of a Bucket object returned by the getBucket handler.
    export interface Bucket {
        _id: string;
        name: string;
        region: string;
        createdAt: string;
    }
  • Imports helper functions for validation and response unwrapping used in the bucket operations.
    import { validateRequired, unwrapApiResponse } from '../utils/errors.js';
  • Uses validation helper to ensure bucket name is provided.
    validateRequired(name, 'Bucket name');
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states a read operation ('Get'), implying it's non-destructive, but doesn't address authentication needs, rate limits, error handling, or response format. For a tool with zero annotation coverage, this is a significant gap in transparency about how the tool behaves.

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 a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loaded with the core action, making it easy to parse quickly.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what details are returned (e.g., bucket properties, status), error scenarios, or any behavioral nuances. For a tool that likely returns structured data, this leaves the agent guessing about the result format and usage context.

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?

The schema description coverage is 100%, with the single parameter 'name' clearly documented in the schema. The description doesn't add any semantic details beyond what the schema provides (e.g., format constraints, examples, or bucket naming rules). This meets the baseline score of 3 since the schema does the heavy lifting for parameter documentation.

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 the verb ('Get') and resource ('details of a specific bucket'), making the purpose understandable. It distinguishes from sibling tools like 'liara_list_buckets' by specifying retrieval of a single bucket rather than listing all. However, it doesn't specify what details are included (e.g., metadata, configuration, status), which prevents a perfect score.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., needing the bucket name), compare it to 'liara_list_buckets' for discovery, or indicate error conditions (e.g., what happens if the bucket doesn't exist). This leaves the agent without context for proper tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/razavioo/liara-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server