Skip to main content
Glama
hyperpolymath

BoJ-server

by hyperpolymath
OverviewSchemaRelated ServersScoreDiscussions

boj_cloud_vercel

Manage Vercel projects by handling deployments, domains, environment variables, logs, and serverless functions through the BoJ-server MCP server.

Instructions

Manage Vercel projects — deployments, domains, environment variables, logs, serverless functions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
operationYesThe Vercel operation
api_tokenNoVercel API token (for authenticate)
paramsNoOperation parameters

Implementation Reference

  • mcp-bridge/main.js:671-677 (handler)
    The handler for the boj_cloud_vercel tool, which dispatches the request to the 'cloud-mcp' cartridge.
    case "boj_cloud_verpex":
case "boj_cloud_cloudflare":
case "boj_cloud_vercel": {
  const result = await invokeCartridge("cloud-mcp", { provider: toolName.replace("boj_cloud_", ""), ...args });
  sendResult(id, { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] });
  break;
}
  • mcp-bridge/main.js:388-400 (schema)
    Registration and input schema definition for the boj_cloud_vercel tool.
    tools.push({
  name: "boj_cloud_vercel",
  description: "Manage Vercel projects — deployments, domains, environment variables, logs, serverless functions",
  inputSchema: {
    type: "object",
    properties: {
      operation: { type: "string", enum: ["authenticate", "list-projects", "get-project", "list-deployments", "get-deployment", "list-domains", "list-env-vars", "deployment-logs", "list-functions"], description: "The Vercel operation" },
      api_token: { type: "string", description: "Vercel API token (for authenticate)" },
      params: { type: "object", description: "Operation parameters" },
    },
    required: ["operation"],
  },
});

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral disclosure. It mentions resource types but doesn't describe authentication requirements (though 'api_token' parameter hints at it), rate limits, error handling, or what 'manage' entails (read vs write operations). The description doesn't contradict annotations since none exist, but it fails to provide adequate behavioral context for a multi-operation cloud management tool.

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, efficient sentence that lists key resource areas. It's appropriately sized and front-loaded with the main purpose ('Manage Vercel projects'). However, it could be slightly more structured by separating operation categories or adding minimal context about the tool's scope.

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?

For a tool with 3 parameters, no annotations, no output schema, and a complex operation enum (9 options), the description is inadequate. It doesn't explain the tool's multi-operation nature, how operations relate to parameters, what results to expect, or any prerequisites. The description leaves too much undefined for effective agent use.

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%, providing good documentation for all 3 parameters. The description adds minimal value beyond the schema—it mentions 'Vercel projects' which aligns with the operation enum, but doesn't explain parameter relationships (e.g., that 'api_token' is specifically for 'authenticate' operation) or provide context for the generic 'params' object. Baseline 3 is appropriate given the schema does most of the work.

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 tool's purpose: 'Manage Vercel projects' with specific resource areas listed (deployments, domains, environment variables, logs, serverless functions). It distinguishes from sibling tools by focusing on Vercel cloud operations rather than browser, GitHub, GitLab, or other domains. However, it doesn't specify the exact verb for each operation beyond 'manage'.

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. It doesn't mention when to choose specific operations (like 'authenticate' vs 'list-projects'), nor does it differentiate from sibling cloud tools like 'boj_cloud_cloudflare' or 'boj_cloud_verpex'. Usage context is implied but not explicit.

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/hyperpolymath/boj-server'

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