Skip to main content
Glama

Two Minute Toolkit

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.

Input Schema

NameRequiredDescriptionDefault
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. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark this read-only/idempotent/closed-world, and the description adds substantial non-obvious behavior: one system renders but is warned, more than 12 are dropped, self-sizing between 880–1280px, 2x PNG rendering, the Edit link, and the critical 'ALWAYS give the user the image link' because inline images can't be saved. It also carries a privacy constraint (first names/roles only, no identifying client details) that nothing else conveys.

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 purpose, then usage routing, then limits, then the link/rendering caveat—a sensible order. It is long and dense for a single paragraph, with the limits list partly duplicating the schema, but nearly every clause carries operational value.

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?

No output schema exists, so the description must describe the artifact, and it does fully—layout, line semantics, legend, sizing, PNG behavior and how to deliver the result. Combined with the rich nested schema, an agent has everything needed to call it correctly and present the output.

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 every parameter and nested field is already documented with examples, enums, defaults and limits; the description mostly restates those limits (2–12 systems, 0–8 members, 1–3 word names, ~10-word details) in summary form. It adds little semantic information beyond the schema, so the baseline applies.

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 resource ('Generate a clean ecomap, Hartman style') and spells out the visual structure it produces—centre circle, 2–12 surrounding systems, line styles, arrowheads, legend. It also explicitly names the sibling tools it is not (hub and spoke, mind map, org chart), so the agent can distinguish it 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; use a hub and spoke for neutral parts..., a mind map when items branch further, and an org chart for reporting lines' gives explicit selection criteria and named alternatives. It further adds the operating instruction to infer missing details rather than asking, which is actionable guidance an agent needs.

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