Skip to main content
Glama

Two Minute Ecomap

create_ecomap
Read-onlyIdempotent

Generate a clean ecomap (ecological map, Hartman style) for social work, family therapy, case management and school counselling: the client or household in a solid centre circle with its members listed inside, and 2–12 system circles around it (school, work, extended family, church, health care, probation, friends…), each joined to the centre by a line whose style shows the relationship: strong (thick line), moderate (plain line, the default), tenuous (dashed) or stressful (hatched red line). Arrowheads show the flow of energy or resources: to the system, from it, or both ways. Each system may carry a short detail outside its circle, and a legend of the line styles sits underneath. Choose it to map a person's or family's relationships with outside systems; use a hub and spoke for neutral parts around a centre with no relationship quality, a mind map when the items branch further, and an org chart for reporting lines. Limits: 2–12 systems, 0–8 household members, system names of 1–3 words, details of about 10 words. Use first names or roles only; never put identifying client details in the chart. 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": "Lopez family ecomap",
      "center": {
        "name": "Lopez household",
        "members": [
          "Maria, 34",
          "Leo, 9"
        ]
      },
      "systems": [
        {
          "flow": "both",
          "name": "School",
          "strength": "strong"
        },
        {
          "flow": "to",
          "name": "Work",
          "detail": "Night shifts",
          "strength": "stressful"
        },
        {
          "name": "Extended family",
          "strength": "tenuous"
        },
        {
          "flow": "from",
          "name": "Health care"
        }
      ]
    },
    "name": "create_ecomap"
  }
}

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.Ecomap
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.
centerYesThe client or household in the middle: a solid circle in the first palette colour with the name in bold white and the members listed under it, e.g. { "name": "Lopez household", "members": ["Maria, 34", "Leo, 9"] }. Use first names, roles or ages only.
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).
legendNoShow the legend under the map explaining the four line styles and the arrows. Default true; set false when the audience already knows the notation.
paletteNoHex colours applied in order to items that have no colour of their own. Pass the user's brand colours here when they name them. Default: indigo, sky, emerald, amber, red, gray.
systemsYesThe systems around the centre (2–12), placed clockwise from 12 o'clock: people, groups and services such as School, Work, Extended family, Church, Health care, Friends, Probation, Benefits. One system still renders but is reported as a warning; more than 12 are dropped.

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 already declare readOnlyHint/idempotentHint/openWorldHint=false, so the safety profile is covered; the description adds genuinely new behavioral context: hard limits (2–12 systems, 0–8 members), a privacy rule ("never put identifying client details"), an instruction to infer missing details rather than ask, and the important caveat that inline chat images cannot be saved so the link must always be given. That last point is exactly the kind of operational detail annotations cannot carry.

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?

Purpose is front-loaded and no sentence is filler, but the opening is an extremely long run-on sentence packing structure, notation, tool-choice and limits together, and the line-style enumeration is repeated almost verbatim from the schema's strength field. It would read better split into a short purpose line plus a constraints line.

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 an eight-parameter nested chart generator with no output schema, the description covers everything an agent needs: what is produced, the numeric limits, the privacy rule, when to pick a sibling, and how the result is delivered back to the user (link rather than inline image). Nothing material is left unresolved.

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 baseline is 3; the description still adds value by restating the practical constraints in prose (2–12 systems, 0–8 household members, 1–3 word names, ~10 word details) and explaining Hartman conventions for the strength and flow enums, which helps an agent populate them correctly. Much of this duplicates the schema, so it is not a 5.

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+resource ("Generate a clean ecomap (ecological map, Hartman style)") and immediately describes the concrete visual structure: centre circle with members, 2–12 system circles, line styles for strength, arrowheads for flow. It explicitly names siblings it is not (hub and spoke, mind map, org chart) with the condition that selects each, so an agent can discriminate without opening a schema.

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?

"Choose it to map a person's or family's relationships with outside systems" gives the positive condition, and the same sentence gives three explicit alternates with their triggering conditions (hub and spoke for neutral parts, mind map for branching items, org chart for reporting lines). The final line also instructs what to always output (the image link) with the reason.

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