Skip to main content
Glama
Sign In
KevinChu1110

driftnet

by KevinChu1110
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get one item

driftnet_get_item
Read-onlyIdempotent

Fetch one catalogued item by id to get details search omits: use cases, images, reader notes, chat comments, linked tools, and related cards. Use after searching when you need the full record.

Instructions

Fetch one item by id with what search results leave out: use cases, try_it, pictures, the reader's note, what people wrote in chat when sharing it, tools found inside it (e.g. the repos a post linked) and up to 5 related cards. Use driftnet_search_items first when you don't have an id yet. id is the number shown in search or save results; ids of trashed items work too and come back with trashed: true, so you can look before restoring. Fails if no item has that id, or if it was flagged for prompt injection (such items are hidden everywhere).

Input Schema

NameRequiredDescriptionDefault
idYesItem id from driftnet_search_items or driftnet_save_link, a positive integer such as 42

Output Schema

NameRequiredDescriptionDefault
itemYes
noticeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.7.0
    • changedInput schema / properties / id / description
      Previous value: -"Item id, as returned by driftnet_search, driftnet_list_recent or driftnet_save"New value: +"Item id from driftnet_search_items or driftnet_save_link, a positive integer such as 42"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "item": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "notice": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "notice",
+    "item"
+  ],
+  "type": "object"
+}
  2. Addedv0.5.1

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover read-only/idempotent/non-destructive, so this score comes from the added behavioral detail: trashed items are reachable and return trashed: true, and injection-flagged items are hard-failed and hidden everywhere. That discloses edge-case behavior an agent could not infer from the structured fields.

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?

Three sentences, front-loaded with purpose then usage then failure modes in a logical order, with no repetition. The first sentence's enumerated payload list is dense and slightly long, but each item conveys something the agent needs.

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?

With an output schema present, return shape need not be explained, and the description still covers what kinds of extra data come back, the prerequisite path (search first), trashed handling, and both failure modes. Nothing an agent needs to call this correctly is missing.

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% and the schema already documents id's origin and positive-integer constraint, so the baseline is 3. The description adds genuine meaning beyond it by clarifying the id is the number rendered in search/save results and that ids of trashed items are accepted.

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 ('Fetch one item by id') and immediately differentiates itself from the sibling search tool by naming the extra detail it returns (use cases, try_it, pictures, chat shares, embedded tools, related cards). An agent can tell exactly why this exists next to driftnet_search_items.

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 routing: 'Use driftnet_search_items first when you don't have an id yet', and explains that trashed ids are valid so an agent can inspect before restoring. It also names two failure conditions (unknown id, prompt-injection flagged items), which is real when-not guidance rather than generic filler.

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