Skip to main content
Glama
Sign In

Tokenrip

by com.tokenrip
OverviewDiscussionsAdmin

Get artifact details

artifact_get
Read-onlyIdempotent

Read authorized artifact metadata by id, alias or page URL. For a workspace member it also lists the tasks that made, have as a result, or use the file (tasks, at most 20, and tasksTotal).

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": {
      "artifactId": "<artifactId>"
    },
    "name": "artifact_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
artifactIdYesThe artifact: its id, its alias (bare, ~agent/alias or _team/alias), or its page URL.

Output Schema

NameRequiredDescriptionDefault
artifactYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / properties / artifact / properties / audience
      Removed value: -{
-  "enum": [
-    "internal",
-    "shared"
-  ],
-  "type": "string"
-}
  2. Changed2 schema fields changed
    • addedOutput schema / properties / artifact / properties / tasks
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "format": "uuid",
+        "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+        "type": "string"
+      },
+      "made": {
+        "type": "boolean"
+      },
+      "result": {
+        "type": "boolean"
+      },
+      "status": {
+        "enum": [
+          "todo",
+          "doing",
+          "review",
+          "done",
+          "cancelled"
+        ],
+        "type": "string"
+      },
+      "title": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "title",
+      "status",
+      "made",
+      "result"
+    ],
+    "type": "object"
+  },
+  "maxItems": 20,
+  "type": "array"
+}
    • addedOutput schema / properties / artifact / properties / tasksTotal
      Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
  3. Changed3 schema fields changed
    • addedOutput schema / properties / artifact / properties / currentVersionNumber
      Added value: +{
+  "anyOf": [
+    {
+      "exclusiveMinimum": 0,
+      "maximum": 9007199254740991,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • addedOutput schema / properties / artifact / properties / history
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "from": {
+          "enum": [
+            "file",
+            "folder",
+            "workspace",
+            "default"
+          ],
+          "type": "string"
+        },
+        "value": {
+          "anyOf": [
+            {
+              "enum": [
+                "off",
+                "all"
+              ],
+              "type": "string"
+            },
+            {
+              "maximum": 100,
+              "minimum": 1,
+              "type": "integer"
+            }
+          ]
+        }
+      },
+      "required": [
+        "value",
+        "from"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedOutput schema / properties / artifact / required
      Previous value: -[
-  "id",
-  "url",
-  "rawUrl",
-  "type",
-  "currentVersionId",
-  "alias",
-  "title",
-  "folder",
-  "visibility",
-  "mimeType",
-  "sizeBytes",
-  "versionCount",
-  "ownerId",
-  "parentArtifactId",
-  "publicAsset",
-  "createdAt",
-  "updatedAt"
-]New value: +[
+  "id",
+  "url",
+  "rawUrl",
+  "type",
+  "currentVersionId",
+  "alias",
+  "title",
+  "folder",
+  "visibility",
+  "mimeType",
+  "sizeBytes",
+  "versionCount",
+  "currentVersionNumber",
+  "ownerId",
+  "parentArtifactId",
+  "publicAsset",
+  "history",
+  "createdAt",
+  "updatedAt"
+]
  4. Changed3 schema fields changed
    • addedOutput schema / properties / artifact / properties / folder
      Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "id": {
+          "format": "uuid",
+          "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+          "type": "string"
+        },
+        "slug": {
+          "type": "string"
+        },
+        "teamSlug": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "slug"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • addedOutput schema / properties / artifact / properties / rawUrl
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedOutput schema / properties / artifact / required
      Previous value: -[
-  "id",
-  "url",
-  "type",
-  "currentVersionId",
-  "visibility",
-  "alias",
-  "title",
-  "mimeType",
-  "sizeBytes",
-  "versionCount",
-  "ownerId",
-  "parentArtifactId",
-  "publicAsset",
-  "createdAt",
-  "updatedAt"
-]New value: +[
+  "id",
+  "url",
+  "rawUrl",
+  "type",
+  "currentVersionId",
+  "alias",
+  "title",
+  "folder",
+  "visibility",
+  "mimeType",
+  "sizeBytes",
+  "versionCount",
+  "ownerId",
+  "parentArtifactId",
+  "publicAsset",
+  "createdAt",
+  "updatedAt"
+]
  5. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description goes beyond them by disclosing conditional behavior — workspace members additionally get task linkage, capped at 20 entries with a tasksTotal counter — which an agent would otherwise not anticipate.

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?

Two sentences with no filler, and the core action is front-loaded ahead of the conditional task-listing detail. The clause describing which tasks are included is slightly convoluted but still parses in one read.

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?

For a single-parameter read tool with full annotations and an output schema already documenting return shape, the description covers the essentials and flags the notable tasks/tasksTotal payload. Minor gaps remain around behavior when the artifact is missing or unauthorized, but nothing essential to calling it correctly is absent.

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 coverage is 100% and the artifactId field already documents id, alias (bare, ~agent/alias, _team/alias) and page URL. The description restates the same identifier forms without adding syntax, validation or resolution-precedence detail, so the baseline of 3 applies.

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 and resource ('Read authorized artifact metadata') and states the three accepted identifier forms. It implicitly distinguishes itself from content-reading siblings by specifying 'metadata', but it never names artifact_get_content, so the differentiation is left to the agent.

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?

The word 'authorized' hints at a permission precondition, which is useful context for when the call will succeed. However, there is no explicit statement of when to prefer this over artifact_get_content or artifact_list, so the agent must infer usage from the resource noun alone.

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

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