Skip to main content
Glama

get_capabilities

Retrieve a summary of Carbone's supported formats, features, usage examples, and documentation links. Use this tool to understand what Carbone can do before proceeding.

Instructions

Returns a summary of all Carbone capabilities: supported formats, features, tool usage examples, and links to full documentation. Call this first if you are unsure what Carbone can do.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that returns the capabilities overview text as a tool response.
    export function handleGetCapabilities() {
      return {
        content: [{ type: 'text' as const, text: CAPABILITIES_TEXT }],
      };
    }
  • Schema for get_capabilities (empty object — no input parameters required).
    export const getCapabilitiesSchema = {};
  • Registers the get_capabilities tool with the MCP server, using an empty schema and no client dependency.
    server.registerTool(
      getCapabilitiesToolName,
      { description: getCapabilitiesDescription },
      () => handleGetCapabilities()
    );
  • Tool name constant for get_capabilities.
    export const getCapabilitiesToolName = 'get_capabilities';
    
    export const getCapabilitiesDescription =
      'Returns a summary of all Carbone capabilities: supported formats, features, tool usage examples, ' +
      'and links to full documentation. Call this first if you are unsure what Carbone can do.';
    
    export const getCapabilitiesSchema = {};
    
    const CAPABILITIES_TEXT = `# Carbone — Document Generation & Conversion
  • Description string for the get_capabilities tool.
    export const getCapabilitiesDescription =
      'Returns a summary of all Carbone capabilities: supported formats, features, tool usage examples, ' +
      'and links to full documentation. Call this first if you are unsure what Carbone can do.';
Behavior4/5

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

With no annotations, the description fully conveys that this tool is a read-only operation returning a summary. It does not mention any side effects, auth requirements, or rate limits, but for a simple discovery tool this is adequate.

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?

Two sentences: the first states the function and content, the second gives usage guidance. No extraneous words, and the most important information is front-loaded.

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

Completeness5/5

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

Despite lacking an output schema, the description specifies the kind of information returned (formats, features, examples, links). For a zero-parameter tool, this is complete and sufficient for an agent to decide to use it.

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 input schema has zero parameters with 100% coverage, so the baseline is 3. The description implicitly confirms no parameters are needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns a summary of Carbone capabilities, listing supported formats, features, usage examples, and documentation links. This distinguishes it from sibling tools that perform specific file operations.

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

Usage Guidelines4/5

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

The description explicitly advises to call this tool first when unsure about Carbone's capabilities, providing clear context. It implies not to use it when you know exactly what you need, though it does not list alternative tools.

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/carboneio/carbone-mcp'

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