Skip to main content
Glama
KevinChu1110

driftnet

by KevinChu1110
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Search shared AI tools

driftnet_search
Read-onlyIdempotent

Find vetted AI tools, repos, videos and guides shared in group chats before picking a library by searching names, tags, notes and chat context.

Instructions

Search the reader's catalogue of AI tools, repos, videos and guides that people shared in group chats. Call it before choosing a tool or library for a task: someone may already have vetted one. Matches the query against names, summaries, tags, URLs, the reader's notes and the chat text a link was shared with; an empty query lists the best items. Results are ranked best first (must-see before normal), then most recent, and exclude trashed, down-voted and prompt-injection-flagged items. Each item has id, name, url, folder, kind, worth, one_liner, highlights, tags, times shared and date added. Read-only. Use driftnet_recent instead for a time-window feed.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum items to return, 1–50. Defaults to 10
queryNoFree text, e.g. 'pdf to markdown' or a tool name. Omit to list the best items
categoryNoA folder id from driftnet_folders; includes everything in its sub-folders. Omit for all folders
min_worthNoRating floor: skip < low < normal < must-see. Defaults to 'normal', which hides skipped and low-value items

Output Schema

NameRequiredDescriptionDefault
itemsYes
noticeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.1
    • addedInput schema / properties / category / description
      Added value: +"A folder id from driftnet_folders; includes everything in its sub-folders. Omit for all folders"
    • addedInput schema / properties / limit / description
      Added value: +"Maximum items to return, 1–50. Defaults to 10"
    • changedInput schema / properties / min_worth / description
      Previous value: -"Defaults to 'normal'"New value: +"Rating floor: skip < low < normal < must-see. Defaults to 'normal', which hides skipped and low-value items"
    • changedInput schema / properties / query / description
      Previous value: -"Free text, matched against names, summaries and URLs"New value: +"Free text, e.g. 'pdf to markdown' or a tool name. Omit to list the best items"
    • addedInput schema / properties / query / maxLength
      Added value: +200
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "items": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "added": {
+            "type": "string"
+          },
+          "category": {
+            "type": "string"
+          },
+          "highlights": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "id": {
+            "type": "number"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "one_liner": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "shared": {
+            "type": "number"
+          },
+          "tags": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "url": {
+            "type": "string"
+          },
+          "worth": {
+            "enum": [
+              "skip",
+              "low",
+              "normal",
+              "must-see"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "url",
+          "category",
+          "kind",
+          "worth",
+          "one_liner",
+          "highlights",
+          "tags",
+          "shared",
+          "added"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "notice": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "notice",
+    "items"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered; the description nonetheless adds real behavioral detail: field-level match scope, empty-query fallback, ranking order (best first, then recency) and exclusion rules (trashed, down-voted, injection-flagged). It repeats 'Read-only' (redundant with annotations) and enumerates return fields that the output schema already provides, so it adds context but doesn't fully focus on new information.

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?

Front-loaded with purpose and the call-before-choosing trigger, with no filler sentences. The trailing field enumeration ('id, name, url, folder, kind...') is the one element that doesn't fully earn its place given the output schema.

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 four-optional-parameter read tool with full schema coverage, an output schema and annotations, the description covers corpus scope, matching semantics, ranking, exclusions and sibling routing. The remaining redundancy (listing returned fields) is harmless.

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%, so a 3 is the baseline; the description earns extra by explaining what the query is matched against (names, summaries, tags, URLs, notes, chat text) and what an empty query does. It doesn't clarify category-as-folder-id or min_worth's enum ordering beyond what the schema already says.

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?

States a specific verb and resource ('Search the reader's catalogue of AI tools, repos, videos and guides'), plus the corpus's origin (shared in group chats). This clearly separates it from siblings like driftnet_recent (time-window) and driftnet_get (single item).

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?

Gives explicit when-to-use guidance ('Call it before choosing a tool or library for a task: someone may already have vetted one') and names the alternative for a different need ('Use driftnet_recent instead for a time-window feed'). The empty-query case is also bounded.

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

Deploy Server

Other Tools