Skip to main content
Glama
KevinChu1110

driftnet

by KevinChu1110
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get one item

driftnet_get
Read-onlyIdempotent

Fetch a catalogue item by ID with summaries, use cases, personal notes, chat mentions, and linked tools. Use after searching to inspect one item's full details.

Instructions

Fetch a single catalogue item by id, with everything driftnet knows about it: the summary fields, use cases, the reader's own note, what people wrote in chat when they shared it, and the tools found inside it (e.g. the repos a post linked). Use it after driftnet_search or driftnet_recent when you need the details. Read-only. Fails if no item has that id.

Input Schema

NameRequiredDescriptionDefault
idYesItem id, as returned by driftnet_search, driftnet_recent or driftnet_save

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.1

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description reinforces read-only behavior. It adds useful behavioral detail beyond annotations by stating that it fails when no item has the given id and by describing the breadth of returned data.

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 front-loaded with the core operation, followed by contents, usage context, safety, and failure behavior. Every sentence contributes relevant information without 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 one-parameter read tool with no output schema, the description does enough: it explains what the item contains, when to call it, that it is read-only, and what happens on a missing id.

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 description coverage is 100%, so the single id parameter is already well documented. The description reinforces that lookup is by id and adds the failure condition, but it does not add new syntax or format details beyond the schema.

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 states a specific verb and resource: fetch a single catalogue item by id. It also enumerates what the item includes (summary fields, use cases, notes, chat context, embedded tools), which clearly distinguishes it from search and recent-list siblings.

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?

It explicitly says to use this after driftnet_search or driftnet_recent when details are needed, giving clear context for selection. It does not spell out when not to use it, but the intended usage path is unambiguous.

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