Skip to main content
Glama

Two Minute Porter's Five Forces

create_five_forces
Read-onlyIdempotent

Generate a slide-deck-quality Porter's five forces diagram laid out as the classic cross: competitive rivalry in the centre, threat of new entrants above, threat of substitutes below, bargaining power of suppliers on the left and of buyers on the right, with arrows pointing in at the centre. Each box has a header band with the force's name, an optional rating pill (very low, low, medium, high, very high; green, amber or red) and up to 5 short bullets of evidence; an optional conclusion line sits underneath. Choose it to assess an industry's attractiveness or competitive pressure for a strategy, market-entry, investment or case-interview slide. Use a Harvey ball matrix to score several options against criteria, a hub and spoke for items around a centre with no fixed meaning, and a mind map for open-ended brainstorming. All five forces are required (an empty object {} is fine); infer sensible ratings and bullets from the industry rather than asking. Limits: 5 bullets per force of about 4–10 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": "Five forces: US ride-hailing",
      "buyers": {
        "rating": "high",
        "bullets": [
          "Riders switch apps for a cheaper fare"
        ]
      },
      "rivalry": {
        "rating": "high",
        "bullets": [
          "Two players hold over 95% of trips",
          "Promotions and price matching are constant"
        ]
      },
      "suppliers": {
        "rating": "medium",
        "bullets": [
          "Drivers multi-home across both apps"
        ]
      },
      "conclusion": "Overall: moderately attractive for the two scaled players; buyer power and rivalry cap margins",
      "newEntrants": {
        "rating": "low",
        "bullets": [
          "Two-sided network effects favour incumbents",
          "Insurance and licensing costs are high"
        ]
      },
      "substitutes": {
        "rating": "medium",
        "bullets": [
          "Own car, transit, micromobility"
        ]
      }
    },
    "name": "create_five_forces"
  }
}

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.Five forces analysis
widthNoChart width in pixels (640–2400). Omit it (recommended) and the chart sizes itself to its content with comfortable margins, between 880 and 1280px wide. PNG output renders at 2x.
buyersYesRight box: how much leverage customers have to push prices down or demand more. Default name "Bargaining power of buyers". E.g. { "rating": "high", "bullets": ["Riders compare fares in seconds"] }.
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).
paletteNoHex colours. Every header band takes the FIRST palette colour unless a force sets its own colour; rating pills always use green, amber and red. Default: indigo, sky, emerald, amber, red, gray.
rivalryYesCentre box: how intensely existing competitors fight on price, product, marketing and service. Default name "Competitive rivalry". E.g. { "rating": "high", "bullets": ["Price war among the top two players","Low switching costs for riders"] }.
suppliersYesLeft box: how much leverage suppliers (inputs, labour, platforms) have over prices and terms. Default name "Bargaining power of suppliers". E.g. { "rating": "high", "bullets": ["Drivers multi-home across apps"] }.
conclusionNoOptional one-line takeaway shown in a muted band under the cross, e.g. "Overall: moderately attractive; buyer power is the main threat". Wraps to 2 lines. Omit for none.
newEntrantsYesTop box: how easily new competitors can enter the industry (capital needs, scale, brand, regulation). Default name "Threat of new entrants". E.g. { "rating": "high", "bullets": ["Network effects favour incumbents"] }.
showRatingsNoShow each force's rating pill. Default true; false hides every rating without deleting it.
substitutesYesBottom box: how easily customers can meet the same need another way. Default name "Threat of substitutes". E.g. { "rating": "high", "bullets": ["Public transit and micromobility"] }.

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.6/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnly, idempotent, closed-world), so the bar is lower, yet the description still adds real behavior: infer rather than ask, hard limits (5 bullets of 4–10 words, one-sentence conclusion), the Edit link for post-hoc user adjustment, and the non-obvious instruction to always surface the image link because inline chat images usually cannot be saved. The only unstated piece is what the tool returns on validation failure.

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-loads the artifact and layout, then usage, alternatives, limits and the image-link rule in a logical order with no filler sentences. It is dense but long, and the inference instruction is stated twice ('infer sensible ratings and bullets from the industry rather than asking' followed later by 'Infer missing details rather than asking'), a small redundancy.

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?

For a 12-parameter, deeply nested tool with no output schema, the description covers the visual result, per-force content rules, defaults, overload behavior (infer, don't interrogate), sibling routing, and how the user receives and reuses the output. Nothing an agent needs to call it correctly and hand back the result is missing.

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 coverage is 100%, so baseline is 3, and the description still adds value by mapping each force object to a spatial position in the cross and confirming the required-five-forces rule ('an empty object {} is fine'), which guides how much to fill in. It does not restate the enum values or palette behavior, leaving those to the schema, which is the right division of labor.

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?

States a specific verb and artifact ('Generate a slide-deck-quality Porter's five forces diagram') and immediately pins the exact layout: rivalry centre, entrants above, substitutes below, suppliers left, buyers right. The box contents (header band, rating pill, up to 5 bullets, optional conclusion) make the output unmistakable and clearly separate it from sibling chart tools.

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?

Gives an explicit selection trigger ('assess an industry's attractiveness or competitive pressure for a strategy, market-entry, investment or case-interview slide') and names three siblings with the conditions that select them: harvey matrix for scoring options against criteria, hub and spoke for items around a centre with no fixed meaning, mind map for open-ended brainstorming.

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