Skip to main content
Glama

archive

by io.github.pipeworx-io

Get Metadata

get_metadata
Read-onlyIdempotent

Get full metadata for an archived item by identifier. Returns title, creator, date, format, size, and access details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesArchive.org item identifier (e.g., "principleofrelat00eins", "ApolloMissionsMoonLandings")

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesArchive.org item identifier
urlYesDirect link to item on archive.org
dateYesPublication or creation date
filesYesList of files (first 20)
titleYesItem title
creatorYesList of item creators
languageYesPrimary language of the item
subjectsYesList of subject tags
downloadsYesNumber of downloads
mediatypeYesMedia type
added_dateYesDate item was added to archive
descriptionYesItem description
files_countYesTotal number of files in item
license_urlYesURL to license information
public_dateYesDate item was made public
item_size_bytesYesTotal size of item in bytes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "id": "principleofrelat00eins"
+  },
+  {
+    "id": "ApolloMissionsMoonLandings"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "added_date": {
+      "description": "Date item was added to archive",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "creator": {
+      "description": "List of item creators",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "date": {
+      "description": "Publication or creation date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "description": {
+      "description": "Item description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "downloads": {
+      "description": "Number of downloads",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "files": {
+      "description": "List of files (first 20)",
+      "items": {
+        "properties": {
+          "format": {
+            "description": "File format",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "md5": {
+            "description": "MD5 checksum of file",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "File name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "size_bytes": {
+            "description": "File size in bytes",
+            "type": [
+              "number",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "name",
+          "format",
+          "size_bytes",
+          "md5"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "files_count": {
+      "description": "Total number of files in item",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "Archive.org item identifier",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "item_size_bytes": {
+      "description": "Total size of item in bytes",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "language": {
+      "description": "Primary language of the item",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "license_url": {
+      "description": "URL to license information",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "mediatype": {
+      "description": "Media type",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "public_date": {
+      "description": "Date item was made public",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "subjects": {
+      "description": "List of subject tags",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "title": {
+      "description": "Item title",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "description": "Direct link to item on archive.org",
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "title",
+    "creator",
+    "date",
+    "description",
+    "mediatype",
+    "subjects",
+    "language",
+    "license_url",
+    "added_date",
+    "public_date",
+    "downloads",
+    "files_count",
+    "item_size_bytes",
+    "url",
+    "files"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "url": "https://www.example.com"
-  },
-  {
-    "url": "https://github.com/microlinkhq/sdk"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "author": {
-      "description": "Author of the page content",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "date": {
-      "description": "Publication or modification date",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "description": {
-      "description": "Page description or meta description",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "image": {
-      "description": "Primary image metadata",
-      "properties": {
-        "height": {
-          "description": "Image height in pixels",
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "url": {
-          "description": "Image URL",
-          "type": "string"
-        },
-        "width": {
-          "description": "Image width in pixels",
-          "type": [
-            "number",
-            "null"
-          ]
-        }
-      },
-      "type": [
-        "object",
-        "null"
-      ]
-    },
-    "lang": {
-      "description": "Language of the page",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "logo": {
-      "description": "Logo metadata",
-      "properties": {
-        "height": {
-          "description": "Logo height in pixels",
-          "type": [
-            "number",
-            "null"
-          ]
-        },
-        "url": {
-          "description": "Logo URL",
-          "type": "string"
-        },
-        "width": {
-          "description": "Logo width in pixels",
-          "type": [
-            "number",
-            "null"
-          ]
-        }
-      },
-      "type": [
-        "object",
-        "null"
-      ]
-    },
-    "publisher": {
-      "description": "Publisher of the page",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "title": {
-      "description": "Page title",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "url": {
-      "description": "The URL of the webpage",
-      "type": [
-        "string",
-        "null"
-      ]
-    }
-  },
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "author": {
+      "description": "Author of the page content",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "date": {
+      "description": "Publication or modification date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "description": {
+      "description": "Page description or meta description",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "image": {
+      "description": "Primary image metadata",
+      "properties": {
+        "height": {
+          "description": "Image height in pixels",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "url": {
+          "description": "Image URL",
+          "type": "string"
+        },
+        "width": {
+          "description": "Image width in pixels",
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "lang": {
+      "description": "Language of the page",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "logo": {
+      "description": "Logo metadata",
+      "properties": {
+        "height": {
+          "description": "Logo height in pixels",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "url": {
+          "description": "Logo URL",
+          "type": "string"
+        },
+        "width": {
+          "description": "Logo width in pixels",
+          "type": [
+            "number",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "publisher": {
+      "description": "Publisher of the page",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "title": {
+      "description": "Page title",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url": {
+      "description": "The URL of the webpage",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "url": "https://www.example.com"
+  },
+  {
+    "url": "https://github.com/microlinkhq/sdk"
+  }
+]
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already establish read-only and non-destructive behavior. The description adds useful context by specifying the tool returns title, creator, date, format, size, and access details, going beyond the annotation info.

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 description is two concise sentences, front-loaded with the action and resource. Every word adds value, with no redundancy.

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 one fully documented parameter and an output schema, the description covers all essential behavior. It is complete and sufficient for the agent to select and invoke correctly.

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?

The schema fully describes the single 'id' parameter with examples and 100% coverage. The description adds no further semantic detail, so the baseline score of 3 applies.

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 clearly states the tool's purpose: 'Get full metadata for an archived item by identifier.' This specific verb+resource scope distinguishes it from sibling tools like search or list_files.

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

Usage Guidelines4/5

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

The description clearly implies usage when an identifier is available, but it does not explicitly name alternatives or exclusions. It provides clear context (by identifier) without explicit when-not-to-use guidance.

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

All archive toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation2/5

The ask_pipeworx family (ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research) has significant boundary blurring—ask_pipeworx_beta explicitly 'currently matches ask_pipeworx exactly'—and the six prediction-market tools (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) have heavily overlapping edge-detection purposes. Only the archive, memory, and subscription families are cleanly delineated.

Naming Consistency3/5

There are consistent family prefixes (ask_*, polymarket_*, pipeworx_*) and clean pluralized lists (list_files, list_subscriptions), but the full set mixes bare verbs (remember, recall, forget, search), nouns (entity_profile), and varying patterns (bet_research vs compare_entities, search vs search_within vs recent_changes). Readable in clusters, but no single naming convention binds the set.

Tool Count2/5

35 tools is heavy, and the count is fattened by five distinct product areas—data routing, prediction markets, archive.org access, memory, and subscriptions—that have little to do with each other or with the server name 'archive'. It sits in the 25+ heavy zone even before honoring the mismatch between its name and the sprawl of its purpose.

Completeness3/5

Individual subdomains are well-covered: the memory trio (remember/recall/forget), subscription lifecycle (subscribe/unsubscribe/list_subscriptions/recent_alerts), and archive lineup (search/get_metadata/list_files/wayback_check) are each complete, and extra machinery like pipeworx_feedback and recent_changes shows domain care. But the unifying domain is incoherent—a server named 'archive' that's also a universal data router and prediction-market toolkit—and the scope ends up both bloated and still full of gaps for any one of the intended users (e.g. no archive-item upload, no prediction-market portfolio management).

Resources