Skip to main content
Glama

get_capabilities

Retrieve a full summary of Carbone capabilities including formats, features, examples, and documentation links. Call this first to understand what Carbone can do.

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

  • Registration of the 'get_capabilities' tool on the MCP server using getCapabilitiesToolName, description, and handler.
    server.registerTool(
      getCapabilitiesToolName,
      { description: getCapabilitiesDescription },
      () => handleGetCapabilities()
    );
  • Schema for get_capabilities — an empty object (no input parameters required).
    export const getCapabilitiesSchema = {};
  • Handler function that returns the capabilities text as MCP content.
    export function handleGetCapabilities() {
      return {
        content: [{ type: 'text' as const, text: CAPABILITIES_TEXT }],
      };
    }
  • Tool name constant ('get_capabilities') and description string.
    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.';
Behavior4/5

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

No annotations provided, but the description accurately conveys a read-only introspection operation. It could explicitly state no side effects, but the nature of 'get' and 'capabilities' implies safety.

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 concise sentences: first defines output, second gives usage guidance. No wasted words, front-loaded with essential information.

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?

Given no parameters and no output schema, the description fully explains the tool's purpose and return content. It is complete for a capability discovery tool among action-oriented siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema is empty, so the baseline is 4. The description does not need to add parameter meanings, and it correctly indicates no inputs required.

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 including formats, features, examples, and documentation links. It distinguishes itself from sibling tools by being a discovery tool.

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

Usage Guidelines5/5

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

Explicitly advises to 'Call this first if you are unsure what Carbone can do,' providing clear context for when to use this tool versus other specific action 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