Skip to main content
Glama

GuestGraph

by io.guestgraph
OverviewDiscussionsAdmin

diagram

Read-only

A picture of the model as Mermaid; edge data: list_references. Input: shape; id, domain, type or unit narrow it. aggregate, flow, lifecycle take a context's id; organization without id draws the company; system a landscape, holds its data; usecase, scenario a use case's; requirements a feature's, product's, use case's or requirement's. Returns mermaid, nodes, links, units, counts. Max 50 nodes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idNoThe process, the entity at a neighborhood's middle, the bounded context of a context map, or the aggregate or bounded context of an aggregate, flow or lifecycle picture, the group an organization is narrowed to, or the system drawn in its landscape by system and by the data it holds by holds, the use case drawn by usecase and scenario, or the feature, product, use case or requirement whose requirements are drawn, never by neighborhood
typeNoA type, to draw its schema and the types it is declared with
unitNocore or a pack, to draw that unit's types and what they declare; a meta-model too large to draw whole is drawn as core, and `units` in the answer names every unit
shapeYes
domainNoA domain's id or address, to draw its concepts

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
unitNo
actorNo
edgesYes
linksYes
modelYes
nodesYes
shapeYes
stepsNo
titleYes
unitsNo
mermaidYes
omittedYes
everyTypeNo
extensionsNo
transitionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / unit
      Added value: +{
+  "description": "core or a pack, to draw that unit's types and what they declare; a meta-model too large to draw whole is drawn as core, and `units` in the answer names every unit",
+  "type": "string"
+}
    • addedOutput schema / properties / unit
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / units
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "types": {
+        "maximum": 9007199254740991,
+        "minimum": 0,
+        "type": "integer"
+      },
+      "unit": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "unit",
+      "types"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
  2. Changed6 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"The process, the entity at a neighborhood's middle, the bounded context of a context map, or the aggregate or bounded context of an aggregate, flow or lifecycle picture, the group an organization is narrowed to, or the system drawn in its landscape by system and by the data it holds by holds, never by neighborhood"New value: +"The process, the entity at a neighborhood's middle, the bounded context of a context map, or the aggregate or bounded context of an aggregate, flow or lifecycle picture, the group an organization is narrowed to, or the system drawn in its landscape by system and by the data it holds by holds, the use case drawn by usecase and scenario, or the feature, product, use case or requirement whose requirements are drawn, never by neighborhood"
    • changedInput schema / properties / shape / enum
      Previous value: -[
-  "concepts",
-  "process",
-  "neighborhood",
-  "schema",
-  "context",
-  "aggregate",
-  "flow",
-  "lifecycle",
-  "organization",
-  "system",
-  "holds"
-]New value: +[
+  "concepts",
+  "process",
+  "neighborhood",
+  "schema",
+  "context",
+  "aggregate",
+  "flow",
+  "lifecycle",
+  "organization",
+  "system",
+  "holds",
+  "usecase",
+  "scenario",
+  "requirements"
+]
    • addedOutput schema / properties / actor
      Added value: +{
+  "type": "string"
+}
    • addedOutput schema / properties / extensions
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "condition": {
+        "type": "string"
+      },
+      "handling": {
+        "type": "string"
+      },
+      "step": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "step",
+      "condition",
+      "handling"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedOutput schema / properties / shape / enum
      Previous value: -[
-  "concepts",
-  "process",
-  "neighborhood",
-  "schema",
-  "context",
-  "aggregate",
-  "flow",
-  "lifecycle",
-  "organization",
-  "system",
-  "holds"
-]New value: +[
+  "concepts",
+  "process",
+  "neighborhood",
+  "schema",
+  "context",
+  "aggregate",
+  "flow",
+  "lifecycle",
+  "organization",
+  "system",
+  "holds",
+  "usecase",
+  "scenario",
+  "requirements"
+]
    • addedOutput schema / properties / steps
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "action": {
+        "type": "string"
+      },
+      "actor": {
+        "type": "string"
+      },
+      "step": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "step",
+      "actor",
+      "action"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
  3. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"The process, the entity at a neighborhood's middle, the bounded context of a context map, or the aggregate or bounded context of an aggregate, flow or lifecycle picture, the group an organization is narrowed to, or the system of a system or holds picture"New value: +"The process, the entity at a neighborhood's middle, the bounded context of a context map, or the aggregate or bounded context of an aggregate, flow or lifecycle picture, the group an organization is narrowed to, or the system drawn in its landscape by system and by the data it holds by holds, never by neighborhood"
  4. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"The process, the entity at a neighborhood's middle, the bounded context of a context map, or the aggregate or bounded context of an aggregate, flow or lifecycle picture, or the group an organization is narrowed to"New value: +"The process, the entity at a neighborhood's middle, the bounded context of a context map, or the aggregate or bounded context of an aggregate, flow or lifecycle picture, the group an organization is narrowed to, or the system of a system or holds picture"
    • changedInput schema / properties / shape / enum
      Previous value: -[
-  "concepts",
-  "process",
-  "neighborhood",
-  "schema",
-  "context",
-  "aggregate",
-  "flow",
-  "lifecycle",
-  "organization"
-]New value: +[
+  "concepts",
+  "process",
+  "neighborhood",
+  "schema",
+  "context",
+  "aggregate",
+  "flow",
+  "lifecycle",
+  "organization",
+  "system",
+  "holds"
+]
    • changedOutput schema / properties / shape / enum
      Previous value: -[
-  "concepts",
-  "process",
-  "neighborhood",
-  "schema",
-  "context",
-  "aggregate",
-  "flow",
-  "lifecycle",
-  "organization"
-]New value: +[
+  "concepts",
+  "process",
+  "neighborhood",
+  "schema",
+  "context",
+  "aggregate",
+  "flow",
+  "lifecycle",
+  "organization",
+  "system",
+  "holds"
+]
  5. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"The process, the entity at a neighborhood's middle, the bounded context of a context map, or the aggregate or bounded context of an aggregate, flow or lifecycle picture"New value: +"The process, the entity at a neighborhood's middle, the bounded context of a context map, or the aggregate or bounded context of an aggregate, flow or lifecycle picture, or the group an organization is narrowed to"
    • changedInput schema / properties / shape / enum
      Previous value: -[
-  "concepts",
-  "process",
-  "neighborhood",
-  "schema",
-  "context",
-  "aggregate",
-  "flow",
-  "lifecycle"
-]New value: +[
+  "concepts",
+  "process",
+  "neighborhood",
+  "schema",
+  "context",
+  "aggregate",
+  "flow",
+  "lifecycle",
+  "organization"
+]
    • changedOutput schema / properties / shape / enum
      Previous value: -[
-  "concepts",
-  "process",
-  "neighborhood",
-  "schema",
-  "context",
-  "aggregate",
-  "flow",
-  "lifecycle"
-]New value: +[
+  "concepts",
+  "process",
+  "neighborhood",
+  "schema",
+  "context",
+  "aggregate",
+  "flow",
+  "lifecycle",
+  "organization"
+]
  6. Changed4 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"The process, the entity at a neighborhood's middle, the bounded context of a context map, or the aggregate or bounded context of an aggregate picture"New value: +"The process, the entity at a neighborhood's middle, the bounded context of a context map, or the aggregate or bounded context of an aggregate, flow or lifecycle picture"
    • changedInput schema / properties / shape / enum
      Previous value: -[
-  "concepts",
-  "process",
-  "neighborhood",
-  "schema",
-  "context",
-  "aggregate"
-]New value: +[
+  "concepts",
+  "process",
+  "neighborhood",
+  "schema",
+  "context",
+  "aggregate",
+  "flow",
+  "lifecycle"
+]
    • changedOutput schema / properties / shape / enum
      Previous value: -[
-  "concepts",
-  "process",
-  "neighborhood",
-  "schema",
-  "context",
-  "aggregate"
-]New value: +[
+  "concepts",
+  "process",
+  "neighborhood",
+  "schema",
+  "context",
+  "aggregate",
+  "flow",
+  "lifecycle"
+]
    • addedOutput schema / properties / transitions
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "aggregate": {
+        "type": "string"
+      },
+      "command": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "from": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "to": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "aggregate",
+      "from",
+      "to",
+      "command"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
  7. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"The process to draw, or the entity at the middle of a neighborhood"New value: +"The process, the entity at a neighborhood's middle, the bounded context of a context map, or the aggregate or bounded context of an aggregate picture"
    • changedInput schema / properties / shape / enum
      Previous value: -[
-  "concepts",
-  "process",
-  "neighborhood",
-  "schema"
-]New value: +[
+  "concepts",
+  "process",
+  "neighborhood",
+  "schema",
+  "context",
+  "aggregate"
+]
    • changedOutput schema / properties / shape / enum
      Previous value: -[
-  "concepts",
-  "process",
-  "neighborhood",
-  "schema"
-]New value: +[
+  "concepts",
+  "process",
+  "neighborhood",
+  "schema",
+  "context",
+  "aggregate"
+]
  8. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"A domain's id, to draw its concepts"New value: +"A domain's id or address, to draw its concepts"
  9. Changed5 schema fields changed
    • changedInput schema / properties / shape / enum
      Previous value: -[
-  "concepts",
-  "process",
-  "neighborhood"
-]New value: +[
+  "concepts",
+  "process",
+  "neighborhood",
+  "schema"
+]
    • addedInput schema / properties / type
      Added value: +{
+  "description": "A type, to draw its schema and the types it is declared with",
+  "type": "string"
+}
    • addedOutput schema / properties / everyType
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "multiplicity": {
+        "type": "string"
+      },
+      "to": {
+        "type": "string"
+      },
+      "via": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "via",
+      "to",
+      "multiplicity"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / nodes / items / properties / url
      Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
    • changedOutput schema / properties / shape / enum
      Previous value: -[
-  "concepts",
-  "process",
-  "neighborhood"
-]New value: +[
+  "concepts",
+  "process",
+  "neighborhood",
+  "schema"
+]
  10. Changed2 schema fields changed
    • addedOutput schema / properties / links
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "from": {
+        "type": "string"
+      },
+      "label": {
+        "type": "string"
+      },
+      "to": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "from",
+      "to",
+      "label"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedOutput schema / required
      Previous value: -[
-  "shape",
-  "title",
-  "mermaid",
-  "nodes",
-  "edges",
-  "omitted",
-  "model"
-]New value: +[
+  "shape",
+  "title",
+  "mermaid",
+  "nodes",
+  "links",
+  "edges",
+  "omitted",
+  "model"
+]
  11. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false, and the description adds genuinely new behavior: the returned keys (mermaid, nodes, links, units, counts) and a hard 'Max 50 nodes' size cap. The cap is exactly the kind of constraint an agent needs before invoking.

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

Conciseness3/5

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

There is no filler, but the middle section is a cryptic run-on of comma-spliced clauses that is hard to parse and not clearly front-loaded beyond the opening clause. Compactness comes at the cost of readability.

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?

With 14 shape values, an output schema already covering returns, and 5 parameters, the description supplies the missing piece: the shape-to-parameter mapping plus the node limit. An agent can select the right shape and id after reading it, though a few shape/parameter combos remain guesswork.

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?

With 80% schema coverage the baseline is 3, but the description goes further by mapping which shapes consume which parameters (id applies to aggregate/flow/lifecycle/organization/system/usecase/scenario/requirements, never neighborhood). This is meaningful routing information beyond the schema, though the dense comma-splicing leaves some cases ambiguous.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific output (a Mermaid picture of the model) and distinguishes it from a sibling by steering edge data to list_references. It is clear what the tool produces, though the run-on phrasing makes the resource it draws somewhat implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives shape-by-shape conditions (aggregate/flow/lifecycle need a context id; organization without id draws the company) and routes edge-data needs to list_references. However, it never states when to choose diagram over nearby siblings like describe_schema or get_entity, so the routing guidance is partial.

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

All GuestGraph toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources