Skip to main content
Glama

Morpha

by ai.morphareels
OverviewDiscussionsAdmin

List projects

list_projects
Read-only

List projects as { id, name, editorUrl } entries. The id is what every other tool's projectId argument takes. name is the human-readable label shown in the editor's project picker ("Untitled" when no name has been set — ids are opaque and never shown to the user, so always refer to a project by its name). editorUrl is a tappable link that opens that project in the editor — offer it to the user (by name) when they want to look at one. By default lists the user's OWN personal projects (those not in any workspace). Pass workspaceId (from list_workspaces) to instead list the projects that live in that workspace — including teammates' — each with the owner's ownerEmail. Call this when the user asks "what projects do I have?" or hasn't named a project but you need to operate on one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdNoOptional workspace id (from list_workspaces). When given, lists that workspace's projects instead of the caller's personal ones; requires membership. Omit for personal projects.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYesWhether the call succeeded.
dataNoThe caller's projects.
noteNoWhat to do next when not ready.
errorNoWhy it failed.
statusNoFor cache-backed readers: whether the answer was ready.
editorUrlNoOpens this project in the editor.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / anonymousToken
      Removed value: -{
-  "description": "The token create_anonymous_account returned. This connection has no Morpha key, so every call carries it.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "anonymousToken"
-]New value: +[]
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "description": "The result envelope every Morpha tool returns.",
+  "properties": {
+    "data": {
+      "description": "The caller's projects.",
+      "properties": {
+        "claimUrl": {
+          "description": "Present only when the caller is an anonymous account: the link that hands its projects to a person.",
+          "type": "string"
+        },
+        "projects": {
+          "description": "One entry per project, newest first.",
+          "items": {
+            "description": "One project.",
+            "properties": {
+              "editorUrl": {
+                "description": "A link that opens this project in the editor.",
+                "type": "string"
+              },
+              "id": {
+                "description": "Opaque project id: what every other tool's `projectId` takes.",
+                "type": "string"
+              },
+              "name": {
+                "description": "The label a person sees (\"Untitled\" when unnamed). Refer to a project by this, never by its id.",
+                "type": "string"
+              }
+            },
+            "required": [
+              "id",
+              "name",
+              "editorUrl"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "projects"
+      ],
+      "type": "object"
+    },
+    "editorUrl": {
+      "description": "Opens this project in the editor.",
+      "type": "string"
+    },
+    "error": {
+      "description": "Why it failed.",
+      "type": "string"
+    },
+    "note": {
+      "description": "What to do next when not ready.",
+      "type": "string"
+    },
+    "ok": {
+      "description": "Whether the call succeeded.",
+      "type": "boolean"
+    },
+    "status": {
+      "description": "For cache-backed readers: whether the answer was ready.",
+      "enum": [
+        "ready",
+        "not-ready"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok"
+  ],
+  "type": "object"
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / anonymousToken
      Added value: +{
+  "description": "The token create_anonymous_account returned. This connection has no Morpha key, so every call carries it.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "anonymousToken"
+]
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description does not contradict this. It adds valuable context: the default scope (personal projects), the meaning of id vs. name (ids opaque, names human-readable), and the editorUrl usage. It also explains the membership requirement for workspace listing, going beyond the schema.

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?

The description is comprehensive but not bloated. It is logically structured: output fields first, then default behavior, then workspace parameter, then usage cues. Every sentence adds information without redundancy, though it is a bit longer than strictly necessary.

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 simple read-only tool with an output schema, the description covers everything needed to call it correctly: the output format, the default behavior, the optional parameter, and when to invoke it. Nothing essential 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% (workspaceId has a description), so the baseline is 3. The description adds value by explaining where to get the value (from list_workspaces), what it does (lists workspace projects including teammates'), and that it returns ownerEmail. This goes beyond the schema's brief description.

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?

The description states a specific verb ('List'), resource ('projects'), and the exact output shape ('{ id, name, editorUrl }'), which distinguishes it from siblings like list_workspaces and list_versions. It also explains the semantics of each field, making the tool's purpose unmistakable.

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?

It explicitly gives the trigger conditions ('Call this when the user asks "what projects do I have?" or hasn't named a project but you need to operate on one') and explains the alternative behavior when workspaceId is provided, pointing to list_workspaces as the source. This is clear guidance on when and how to use it.

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

All Morpha toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources