Skip to main content
Glama
Sign In

SpecStream

by ai.specstream
OverviewDiscussionsAdmin

Save a view

save_view

Saves the filters, columns, sort order and map area of a collection as a personal view.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "expected_version": "<expected_version>",
      "view": "<view>",
      "collection_id": "<collection_id>"
    },
    "name": "save_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewYes
collection_idYes
expected_versionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $defs / WorkspaceSavedView / properties / area / anyOf
      Previous value: -[
-  {
-    "items": {
-      "maxItems": 2,
-      "minItems": 2,
-      "prefixItems": [
-        {
-          "type": "number"
-        },
-        {
-          "type": "number"
-        }
-      ],
-      "type": "array"
-    },
-    "maxItems": 2,
-    "minItems": 2,
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "items": {
+        "type": "number"
+      },
+      "maxItems": 2,
+      "minItems": 2,
+      "prefixItems": [
+        {
+          "type": "number"
+        },
+        {
+          "type": "number"
+        }
+      ],
+      "type": "array"
+    },
+    "maxItems": 2,
+    "minItems": 2,
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
  2. First observed

TDQS

B3/5.0
Behavior3/5

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

The annotations already establish that this is a non-read-only, non-destructive, closed-world operation, and the description adds useful context about what state is captured. However, it does not disclose overwrite behavior, permission requirements, or how expected_version prevents conflicting saves.

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?

The definition is a single front-loaded sentence with no wasted wording. It immediately states the action and lists the relevant saved attributes.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has a nested object, three required parameters, no output schema, and no parameter descriptions, so the description carries substantial burden. It explains the saved content but leaves out concurrency semantics for expected_version and does not describe what happens when a view already exists.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It conceptually maps filters, columns, sort order, and map area to parts of the nested view object, but it omits any explanation of expected_version, collection_id, the view id/name, or the view-type enum.

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 uses a specific verb, "Saves," and a specific resource, "personal view," and enumerates the saved state: filters, columns, sort order, and map area. It is clear what the tool does, though it does not explicitly distinguish itself from siblings such as list_views or filter_collection.

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 guidance on when to use this tool versus alternatives, nor any stated prerequisites. The purpose implies saving a view, but the description does not say whether this creates a new view, updates an existing one, or when an agent should prefer this over list_views or filter_collection.

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

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