Skip to main content
Glama

Two Minute SWOT Analysis

create_swot
Read-onlyIdempotent

Generate a slide-deck-quality SWOT analysis laid out as the classic 2×2 grid: Strengths (top left) and Weaknesses (top right) as the internal row, Opportunities (bottom left) and Threats (bottom right) as the external row, each a softly tinted panel with its big coloured letter and up to 8 bullets, with optional Helpful / Harmful and Internal / External axis labels, an optional subject ("Acme Coffee, FY26") and an optional one-line conclusion underneath. Choose it to assess a company, product, team, project or person for a strategy, business-plan, marketing or coursework slide; use Porter's five forces (create_five_forces) for the pressures on a whole industry, a Harvey ball matrix to score options against criteria, and an issue tree to break one problem down. Only strengths is required (an empty [] is fine), but fill all four; infer 3–5 bullets each from context rather than asking. Limits: 8 bullets per quadrant of about 3–8 words, a conclusion of one sentence. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "SWOT: wholesale expansion",
      "subject": "Northside Roasters, FY26",
      "threats": [
        "Green coffee prices at a 40-year high"
      ],
      "strengths": [
        "Award-winning single-origin range",
        "Loyal following at our two cafés"
      ],
      "conclusion": "Go after office wholesale, but fund a second roaster first",
      "weaknesses": [
        "One 15 kg roaster, near capacity"
      ],
      "opportunities": [
        "Offices restocking coffee after hybrid return"
      ]
    },
    "name": "create_swot"
  }
}

Input Schema

NameRequiredDescriptionDefault
lookNoDrawing style, the same in every tool. "regular": clean lines and Inter (the default). "bold": heavier, slightly larger type and thicker lines, for slides read from a distance. "sketch": hand-drawn, with a handwriting font and pen lines that wobble a little, for early ideas and workshops. Use the one the user asks for; otherwise leave it out.regular
titleNoHeading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it.SWOT analysis
widthNoChart width in pixels (640–2400, default 1280, which suits a 16:9 slide). PNG output renders at 2x. Height is computed from the content.
colorsNoOptional colour overrides per quadrant, as hex, e.g. { "threats": "#b91c1c" }. Each colours that quadrant's stripe, letter, bullet dots and tint. Default: emerald, amber, sky and red (or the brand palette).
creditNoShows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding).
labelsNoShow the axis labels: "Helpful" and "Harmful" over the columns, "Internal" and "External" beside the rows. Default true.
paletteNoHex colours. With the default palette the quadrants are emerald (S), amber (W), sky (O) and red (T); pass brand colours and they apply in order S, W, O, T instead. Default: indigo, sky, emerald, amber, red, gray.
subjectNoOptional subject of the analysis, e.g. "Northside Roasters, FY26", shown small and muted in the title row's right corner (or above the grid when the title is long). Omit for none.
threatsNoExternal, harmful: what could hurt the subject, e.g. ["Green coffee prices at a 40-year high"]. 0–8 short phrases. Bottom-right quadrant. Default [].
strengthsYesRequired (may be empty []). Internal, helpful: what the subject does well or owns, e.g. ["Award-winning single-origin range", "Loyal café following"]. 0–8 short phrases of about 3–8 words; long ones wrap to 3 lines. Top-left quadrant.
conclusionNoOptional one-line takeaway shown in a muted band under the grid, e.g. "Lead with wholesale to offices; fund a second roaster first". Wraps to 2 lines. Omit for none.
weaknessesNoInternal, harmful: what holds the subject back, e.g. ["One roaster, near capacity"]. 0–8 short phrases. Top-right quadrant. Default [].
opportunitiesNoExternal, helpful: trends or openings the subject could use, e.g. ["Offices restocking coffee after hybrid return"]. 0–8 short phrases. Bottom-left quadrant. Default [].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / look
      Added value: +{
      +  "default": "regular",
      +  "description": "Drawing style, the same in every tool. \"regular\": clean lines and Inter (the default). \"bold\": heavier, slightly larger type and thicker lines, for slides read from a distance. \"sketch\": hand-drawn, with a handwriting font and pen lines that wobble a little, for early ideas and workshops. Use the one the user asks for; otherwise leave it out.",
      +  "enum": [
      +    "regular",
      +    "bold",
      +    "sketch"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description doesn't contradict them. It goes beyond them with genuinely useful behavior: it infers missing details rather than interrogating the user, enforces content limits, and warns that inline chat images usually cannot be saved so the returned image link should always be surfaced. It stops short of describing exactly what the response payload contains (image plus link plus Edit link), which is a minor residual gap.

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?

Front-loaded with the artifact shape, then selection guidance, then content rules and the image-link requirement, so an agent reading only the start still knows what it gets. The opening sentence is very long and packs visual detail (tinted panels, big coloured letters) that adds little for an agent choosing or filling parameters.

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

Completeness4/5

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

This is a 13-parameter tool with a nested colours object and no output schema, so the description has real work to do; it covers layout, optionality, bullet and conclusion limits, inference policy, and the fact that the user can adjust the chart via the builder Edit link. What it leaves unstated is the returned payload structure beyond the image link, though the schema's 100% coverage absorbs most parameter risk.

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?

Schema description coverage is 100%, so the schema already documents all 13 parameters including the nested colours object, so baseline is 3. The description adds prioritisation rather than field definitions: only `strengths` is required and an empty [] is acceptable, yet all four quadrants should be filled with 3-5 inferred bullets of 3-8 words and a one-sentence conclusion.

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?

Specific verb and resource ("Generate a ... SWOT analysis") plus a precise description of the artifact: 2x2 grid, quadrant positions, tinted panels, coloured letters, bullets. It also distinguishes itself from adjacent diagram tools by naming create_five_forces for industry pressure, the Harvey ball matrix for option scoring and issue trees for problem decomposition.

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?

Explicit when-to-use ("assess a company, product, team, project or person for a strategy, business-plan, marketing or coursework slide") and explicit when-not ("for the pressures on a whole industry" use Porter's five forces instead). The alternatives are paired with the condition that selects them, so an agent can route without opening sibling schemas.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources