Skip to main content
Glama
PhononX

Carbon Voice

by PhononX

get_workspaces_basic_info

Read-only

Retrieve essential workspace details from Carbon Voice to access conversations and voice memos.

Instructions

Get basic information about a workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function that executes the tool logic by calling the generated simplified API method getAllWorkspacesWithBasicInfo with authentication header and formats the result.
    async (params: unknown, { authInfo }): Promise<McpToolResponse> => {
      try {
        return formatToMCPToolResponse(
          await simplifiedApi.getAllWorkspacesWithBasicInfo(
            setCarbonVoiceAuthHeader(authInfo?.token),
          ),
        );
      } catch (error) {
        logger.error('Error getting workspaces basic info:', { error });
        return formatToMCPToolResponse(error);
      }
    },
  • src/server.ts:805-827 (registration)
    Registration of the MCP tool 'get_workspaces_basic_info' with empty input schema and read-only annotation, including the inline handler.
    server.registerTool(
      'get_workspaces_basic_info',
      {
        description: 'Get basic information about a workspace.',
        inputSchema: z.object({}).shape,
        annotations: {
          readOnlyHint: true,
          destructiveHint: false,
        },
      },
      async (params: unknown, { authInfo }): Promise<McpToolResponse> => {
        try {
          return formatToMCPToolResponse(
            await simplifiedApi.getAllWorkspacesWithBasicInfo(
              setCarbonVoiceAuthHeader(authInfo?.token),
            ),
          );
        } catch (error) {
          logger.error('Error getting workspaces basic info:', { error });
          return formatToMCPToolResponse(error);
        }
      },
    );
  • Generated helper function in the simplified API client that performs the HTTP GET request to retrieve basic workspace information.
    const getAllWorkspacesWithBasicInfo = (
      options?: SecondParameter<typeof mutator>,
    ) => {
      return mutator<WorkspaceBasicInfo[]>(
        { url: `/simplified/workspaces/basic-info`, method: 'GET' },
        options,
      );
    };
  • TypeScript type definition for the output of the getAllWorkspacesWithBasicInfo API call, used for type safety.
    export type GetAllWorkspacesWithBasicInfoResult = NonNullable<
      Awaited<
        ReturnType<
          ReturnType<
            typeof getCarbonVoiceSimplifiedAPI
          >['getAllWorkspacesWithBasicInfo']
        >
      >
    >;
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds no behavioral context beyond what annotations provide—no information about what 'basic information' includes, authentication needs, rate limits, or response format. With annotations covering safety, a baseline 3 is appropriate as the description adds minimal value.

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 with zero wasted words. It's appropriately sized for a simple tool and front-loads the core purpose without unnecessary elaboration.

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?

Given the tool's simplicity (0 parameters, read-only annotations), the description is minimally adequate. However, without an output schema and with no details on what 'basic information' includes or how it differs from other retrieval tools, there are clear gaps that could hinder effective use by an AI agent.

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 has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a baseline 4 since it doesn't need to compensate for any schema gaps.

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 'basic information about a workspace', making the purpose understandable. However, it doesn't distinguish this from potential sibling tools like 'get_folder' or 'get_conversation' which also retrieve workspace-related information, so it lacks sibling differentiation.

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. With sibling tools like 'get_folder' and 'get_conversation' that might retrieve workspace data in different contexts, there's no indication of when this basic info retrieval is preferred or what its scope limitations are.

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/PhononX/cv-mcp-server'

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