Skip to main content
Glama
bizino

BOS MCP Server

by bizino

boscli_system_deploy_status

Check the deployment status of BOS servers by providing a customer identifier. Confirm whether the system is deployed or still in progress.

Instructions

Get deployment status for BOS servers

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerNo

Implementation Reference

  • The handler function that executes the 'boscli_system_deploy_status' tool logic. It makes a GET request to '/boscli/system/deploy-status' endpoint via the BosApiClient, passing optional query params (e.g., customer).
      handler: async (args, client) => client.get('/boscli/system/deploy-status', args),
    },
  • Input schema for the tool: allows an optional 'customer' string parameter to filter deployment status by customer.
    schema: { customer: { type: 'string', optional: true } },
  • Tool definition as a McpTool object in the systemTools array. The tool is registered by name 'boscli_system_deploy_status'.
    {
      name: 'boscli_system_deploy_status',
      description: 'Get deployment status for BOS servers',
      schema: { customer: { type: 'string', optional: true } },
      handler: async (args, client) => client.get('/boscli/system/deploy-status', args),
    },
  • The BosApiClient.get() helper method used by the handler to perform the actual HTTP GET request.
    async get<T>(path: string, params?: Record<string, any>): Promise<T> {
      return this.request<T>('GET', path, undefined, params);
    }
Behavior2/5

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

No annotations are provided, and the description only implies a safe read ('Get') but does not disclose any behavioral traits such as authentication needs, side effects, or response details. The description carries the full burden but falls short.

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 concise sentence, which is efficient for a simple tool. However, it lacks additional structure or elaboration that could enhance clarity without verbosity.

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 tool's simplicity and lack of output schema, the description should at least hint at the format or contents of the deployment status. It does not, leaving the agent without complete context to use the tool effectively.

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?

The schema has one parameter 'customer' with no description, and the tool description does not explain its purpose or usage. With 0% schema description coverage, the description should compensate but fails to add meaning.

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 action ('Get') and resource ('deployment status for BOS servers'), providing a clear purpose. However, it does not differentiate from siblings like boscli_system_git_status or boscli_system_info, which are also status-related tools.

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 given on when to use this tool versus alternatives or any prerequisites. The description lacks context about appropriate scenarios for calling this tool.

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/bizino/bos-mcp'

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