Skip to main content
Glama

Sutra

by com.onrender.sutra-c3or
OverviewDiscussionsAdmin

Open Sutra cluster

get_cluster
Read-onlyIdempotent

Return metadata and memories for one named project cluster.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesExact cluster name using letters, numbers, or hyphens.
limitNoMaximum number of memories to return from the cluster.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
clusterYes
memoriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of memories to return from the cluster."
    • addedInput schema / properties / name / description
      Added value: +"Exact cluster name using letters, numbers, or hyphens."
    • addedInput schema / properties / name / maxLength
      Added value: +50
    • addedInput schema / properties / name / minLength
      Added value: +1
    • addedInput schema / properties / name / pattern
      Added value: +"^[A-Za-z0-9-]{1,50}$"
    • removedOutput schema / additionalProperties
      Removed value: -true
    • addedOutput schema / properties
      Added value: +{
+  "cluster": {
+    "properties": {
+      "created_at": {
+        "type": "string"
+      },
+      "description": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "is_default": {
+        "type": "boolean"
+      },
+      "memory_count": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "name": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "description",
+      "is_default",
+      "created_at",
+      "memory_count"
+    ],
+    "type": "object"
+  },
+  "memories": {
+    "items": {
+      "properties": {
+        "cluster": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "content": {
+          "type": "string"
+        },
+        "created_at": {
+          "type": "string"
+        },
+        "importance": {
+          "type": "integer"
+        },
+        "source_agent": {
+          "type": "string"
+        },
+        "tags": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        }
+      },
+      "required": [
+        "content",
+        "source_agent",
+        "importance",
+        "created_at",
+        "tags"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  }
+}
    • addedOutput schema / required
      Added value: +[
+  "cluster",
+  "memories"
+]
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description adds that the result includes both metadata and memories, which is modest context but does not mention error behavior for a missing cluster.

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

Conciseness5/5

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

A single front-loaded sentence that names the action, the payload (metadata and memories) and the scope (one named cluster). Nothing is wasted.

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 an output schema present and annotations covering read-only semantics, the description needn't explain returns. It is nearly complete, though it omits any note about unknown cluster names or the relationship to list_clusters.

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 both the exact-name constraint and the limit/default are fully documented in the schema. The description adds no meaning beyond that, making the baseline 3 correct.

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?

States a specific verb (Return) and resource (metadata and memories for one named project cluster), and 'one named' implies single-cluster lookup versus the sibling list_clusters. It does not explicitly name or contrast with list_clusters, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use guidance and no mention of the alternative list_clusters for discovering valid names, nor any exclusion. Usage is only implied by the required 'name' parameter.

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

All Sutra 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