Skip to main content
Glama

boj_cartridge_info

Retrieve detailed specifications for BoJ-server cartridges to understand their capabilities and integration requirements.

Instructions

Get detailed information about a specific BoJ cartridge

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCartridge name (e.g. database-mcp, container-mcp, git-mcp)

Implementation Reference

  • The handler function that executes the logic for 'boj_cartridge_info' by fetching info from the BOJ API or falling back to offline menu.
    async function fetchCartridgeInfo(name) {
      if (!isValidCartridgeName(name)) {
        return { error: `Invalid cartridge name: ${name}` };
      }
      try {
        const res = await fetch(`${BOJ_BASE}/cartridge/${encodeURIComponent(name)}`);
        return await res.json();
      } catch {
        const all = OFFLINE_MENU.tier_teranga.concat(OFFLINE_MENU.tier_shield);
        const found = all.find(c => c.name === name);
        return found || { error: `Unknown cartridge: ${name}` };
      }
    }
  • The tool invocation handler that routes the 'boj_cartridge_info' request to the implementation function.
    case "boj_cartridge_info": {
      const info = await fetchCartridgeInfo(args.name);
      sendResult(id, {
        content: [
          { type: "text", text: JSON.stringify(info, null, 2) },
        ],
      });
      break;
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a read operation ('Get'), but doesn't mention authentication needs, rate limits, error conditions, or what 'detailed information' includes (e.g., format, fields). For a tool with zero annotation coverage, this is insufficient.

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 gets straight to the point with zero wasted words. It's appropriately sized for a simple lookup tool and front-loads the core purpose.

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?

For a simple single-parameter lookup tool with good schema coverage but no annotations and no output schema, the description is minimally adequate. It states what the tool does but lacks behavioral context and usage guidance. The absence of output schema means the description should ideally hint at return format, which it doesn't.

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 schema already documents the single parameter 'name' with examples. The description doesn't add any parameter semantics beyond what's in the schema (e.g., doesn't clarify what constitutes a valid cartridge name beyond the examples). Baseline 3 is appropriate when schema does 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 verb ('Get') and resource ('detailed information about a specific BoJ cartridge'), making the purpose understandable. However, it doesn't distinguish this tool from its sibling 'boj_cartridges' (which likely lists cartridges rather than providing detailed info about a specific one), preventing 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?

The description provides no guidance on when to use this tool versus alternatives like 'boj_cartridges' or 'boj_cartridge_invoke'. It doesn't mention prerequisites, context, or exclusions, leaving the agent to infer usage from the tool name alone.

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