Skip to main content
Glama
davidscoreal

CIA Diagnose

by davidscoreal

business_diagnose

Assess any company across 11 dimensions, quantify revenue leaks, and receive prioritized recommendations with paid, open source, and implementation options.

Instructions

Expert business diagnosis for any company across 11 dimensions.

Send what you know — tools they use, team size, revenue, pain points, location, industry, leadership situation, cash flow, talent gaps, physical operations, anything. Returns Revenue Leak Score + actionable recommendations comparing paid software, open source alternatives, and professional implementation services.

Works for ANY industry. The more context you provide, the more accurate and specific the diagnosis. Even minimal input (just company_name + industry) produces useful results.

11 dimensions analyzed: finanzas, comercial, operaciones, equipo, tecnologia, marketing, clientes, proveedores, legal, estrategia, marketing_digital.

Args: company_name: Name of the company being diagnosed (required). industry: Industry or sector (e.g. 'construction', 'healthcare', 'ecommerce'). Use list_industries to see calibrated benchmarks. team_size: Number of employees (0 if unknown). location_city: City where the company is based. location_country: Country where the company is based. revenue_estimate: ANNUAL revenue range (e.g. '200k-1m', '1m-5m', 'over_10m'). Used to scale the monthly leak estimate. Accept also revenue_range as alias. software_detected: Comma-separated tools/software the company uses (e.g. 'Excel, WhatsApp, QuickBooks, no CRM'). pain_points: Comma-separated problems described by the company (e.g. 'quotes get lost, manual reporting, slow hiring'). physical_operations: Notes on physical/operational challenges (e.g. 'material waste, rework, production delays'). supply_chain_notes: Notes on supply chain or vendor issues (e.g. 'unreliable suppliers, delivery delays'). hiring_challenges: Notes on hiring difficulties (e.g. "can't find skilled workers, high turnover"). skill_gaps: Notes on skill gaps in the team (e.g. 'no data analyst, no digital marketing'). cash_flow_concerns: Notes on cash flow or payment issues (e.g. 'clients pay late, 60+ day invoices'). ar_aging: Accounts receivable aging notes (e.g. '30%% of invoices over 90 days'). decision_maker_role: Role of the person requesting the diagnosis (e.g. 'CEO', 'COO', 'VP Operations'). stress_indicators: Signs of leadership stress or burnout (e.g. 'working weekends, micromanaging, decision fatigue'). growth_stage: Current business stage (e.g. 'growing', 'stagnant', 'declining', 'startup', 'scaling'). niche: Hyper-specific niche/sub-vertical in free text (e.g. 'B2B SaaS for dental clinics', 'modular construction for retail'). Captured for niche targeting and trend analysis. additional_context: Any other relevant information as free text or JSON. contact_email: Email for follow-up (optional, for lead capture). contact_name: Contact name (optional). lang: Language for the diagnosis ('es' for Spanish, 'en' for English).

Returns: dict: Complete diagnosis containing: - company_name (str): Company analyzed - icp_id (str): Detected industry profile - health_score (float): 0-100 Business Health Score — HIGHER = HEALTHIER. A low score marks the worst area / biggest opportunity. (Also mirrored as revenue_leak_score for backward compatibility, same value.) - score_meaning (str): How to read the score (incl. the "100% = new leagues" idea) - growth_mode (bool): True when most areas are strong — keep the conversation going - guidance (str): What to do next (ask more vs. present + 3 options) - estimated_monthly_leak (str): Estimated monthly revenue leak in weak areas - dimensions (list): Per-dimension scores and findings - actions (list): Prioritized recommendations with triple option - validation_questions (list): Questions to refine the diagnosis - summary (str): Executive summary - leadership_insight (str): Leadership-specific observation

On rate limit:
    - error (str): 'rate_limit_exceeded'
    - message_es / message_en (str): Localized error message
    - upgrade_url (str): Registration URL

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
company_nameYes
industryNo
team_sizeNo
location_cityNo
location_countryNo
revenue_estimateNo
revenue_rangeNo
software_detectedNo
pain_pointsNo
physical_operationsNo
supply_chain_notesNo
hiring_challengesNo
skill_gapsNo
cash_flow_concernsNo
ar_agingNo
decision_maker_roleNo
stress_indicatorsNo
growth_stageNo
nicheNo
additional_contextNo
contact_emailNo
contact_nameNo
langNoes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations are minimal (no destructive/readOnly hints), so the description carries the transparency burden. It clearly states that the tool returns a diagnosis dictionary, includes rate limit error handling, and provides a detailed return schema. It does not mention any side effects or permissions, but the output is well-documented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a clear purpose paragraph, then parameter list, then return schema. It is front-loaded with the core value proposition. However, the parameter descriptions are somewhat verbose (e.g., listing all 11 dimensions) and could be more concise without losing clarity.

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 the tool's complexity (23 parameters, many optional, no schema descriptions), the description is exceptionally complete. It covers every parameter meaningfully, explains the return schema in detail, and provides context for usage (any industry, minimal input). The output schema is fully described.

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

Parameters5/5

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

Schema description coverage is 0%, but the description compensates fully with detailed parameter descriptions. Each of the 23 parameters is explained in the 'Args:' section, including format hints (e.g., revenue_estimate as 'ANNUAL revenue range'), aliases, and required vs. optional status. This adds significant value beyond the schema titles.

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's purpose: 'Expert business diagnosis for any company across 11 dimensions.' It uses specific verbs ('diagnose' implied) and identifies the resource (a company's business). It distinguishes itself from sibling tools by detailing the comprehensive output (Revenue Leak Score, actionable recommendations, 11 dimensions).

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 provides solid usage guidance: 'Send what you know...', 'Works for ANY industry.', and 'Even minimal input... produces useful results.' It implicitly suggests when to use this tool (when a broad diagnosis is needed) but does not explicitly contrast with alternatives like quick_scan or tools_recommend, which could score higher.

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/davidscoreal/cia-diagnose'

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