Skip to main content
Glama
G-Hensley
by G-Hensley

Get Business Info

get_business_info

Retrieve business details—strategy, personas, marketing—for Codaissance or TamperTantrum Labs.

Instructions

Get business information for Codaissance or TamperTantrum Labs including strategy, personas, and marketing

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
businessYesWhich business to get info for
includeNoWhich data to include (defaults to all)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYes

Implementation Reference

  • api/mcp.ts:336-377 (registration)
    Registration of the 'get_business_info' tool with MCP server, defining input schema (business enum, include array) and output schema.
    server.registerTool(
      "get_business_info",
      {
        title: "Get Business Info",
        description: "Get business information for Codaissance or TamperTantrum Labs including strategy, personas, and marketing",
        inputSchema: {
          business: z.enum(["codaissance", "tampertantrum-labs"]).describe("Which business to get info for"),
          include: z.array(z.enum(["strategy", "personas", "marketing"])).optional().describe("Which data to include (defaults to all)"),
        },
        outputSchema: textContentOutputSchema,
      },
      async ({ business, include }) => {
        const includeAll = !include || include.length === 0;
        const result: Record<string, unknown> = { business };
    
        if (includeAll || include?.includes("strategy")) {
          try {
            const strategy = await readJsonFile<BusinessStrategy>(`business/${business}/strategy.json`);
            result.strategy = strategy;
          } catch {
            // File may not exist
          }
        }
        if (includeAll || include?.includes("personas")) {
          try {
            const personas = await readJsonFile<PersonasData>(`business/${business}/personas.json`);
            result.personas = personas;
          } catch {
            // File may not exist
          }
        }
        if (includeAll || include?.includes("marketing")) {
          try {
            const marketing = await readJsonFile<MarketingData>(`business/${business}/marketing.json`);
            result.marketing = marketing;
          } catch {
            // File may not exist
          }
        }
        return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
      }
    );
  • Handler function that fetches business strategy, personas, and marketing data from GitHub JSON files based on the 'include' parameter (defaults to all).
    async ({ business, include }) => {
      const includeAll = !include || include.length === 0;
      const result: Record<string, unknown> = { business };
    
      if (includeAll || include?.includes("strategy")) {
        try {
          const strategy = await readJsonFile<BusinessStrategy>(`business/${business}/strategy.json`);
          result.strategy = strategy;
        } catch {
          // File may not exist
        }
      }
      if (includeAll || include?.includes("personas")) {
        try {
          const personas = await readJsonFile<PersonasData>(`business/${business}/personas.json`);
          result.personas = personas;
        } catch {
          // File may not exist
        }
      }
      if (includeAll || include?.includes("marketing")) {
        try {
          const marketing = await readJsonFile<MarketingData>(`business/${business}/marketing.json`);
          result.marketing = marketing;
        } catch {
          // File may not exist
        }
      }
      return { content: [{ type: "text", text: JSON.stringify(result, null, 2) }] };
    }
  • TypeScript interface for BusinessStrategy data shape.
    export interface BusinessStrategy {
      business_type: string;
      founded: string;
      status: string;
      website: string;
      problem_statement: string;
      solution_statement: string;
      mission_statement: string;
      positioning: BusinessPositioning;
      business_model: BusinessModel;
      competitive_landscape: CompetitiveLandscape;
      products: BusinessProducts;
      key_insights: string[];
    }
  • TypeScript interface for PersonasData (persona/anti-persona data shape).
    export interface PersonasData {
      note?: string;
      primary: Persona;
      secondary: Persona;
      tertiary: Persona;
      quaternary: Persona;
      anti_personas: AntiPersona[];
      shared_values: {
        they_believe: string[];
        they_respond_to: string[];
      };
    }
  • TypeScript interface for MarketingData (content strategy, channels, campaigns).
    export interface MarketingData {
      content_strategy: {
        pillars: ContentPillar[];
        content_by_persona: Record<string, string[]>;
      };
      channels: MarketingChannel[];
      campaigns: unknown[];
      metrics_to_track: string[];
    }
Behavior2/5

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

There are no annotations, so the description must convey behavioral traits. It only states 'Get business information', implying a read operation but lacks details on side effects, permissions, rate limits, or data freshness. This is minimal transparency.

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 concise sentence with no filler, front-loading the key purpose. Every word earns its place.

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 many sibling tools and the presence of an output schema (not shown), the description is adequate but minimal. It lacks usage guidelines and behavioral transparency, so it is not fully complete for an agent to confidently select this tool over alternatives.

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 describes both parameters. The description redundantly lists 'strategy, personas, and marketing' which map to the include enum values, but adds no new meaning beyond the schema's enums. Baseline score is appropriate.

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 the resource 'business information for Codaissance or TamperTantrum Labs', and specifies the included data types (strategy, personas, marketing). It effectively communicates the tool's function, though it does not explicitly differentiate from siblings like get_business_roadmap.

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?

No guidance is provided on when to use this tool versus alternative 'get_*' tools, nor any conditions for use or exclusions. The description only implies usage through naming, leaving the agent to infer context without explicit direction.

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/G-Hensley/myself-mcp-server'

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