Skip to main content
Glama
Sign In
io.github.lsmman/fetchive

io.github.lsmman/fetchive

Official
by lsmman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Search the archive

search_archive
Read-onlyIdempotent

Search the full text of archived transcripts and articles to locate saved ideas and sources. Returns matching excerpts with workspace page links.

Instructions

Full-text search across everything archived — transcripts and article bodies, not just titles. Use this to answer questions about what the user has already saved, or to find the source of a half-remembered idea. Returns matching excerpts with the workspace page link where one was recorded.

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": {
      "query": "<query>"
    },
    "name": "search_archive"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already indicate read-only, non-destructive, and idempotent behavior. The description adds context about return format: 'Returns matching excerpts with the workspace page link where one was recorded.' This goes beyond the annotations and clarifies output behavior.

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 three short sentences, with the main purpose front-loaded in the first sentence. Every sentence adds value: purpose, use cases, and return value. No redundancy or fluff.

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?

With a simple two-parameter tool, an output schema, and strong annotations, the description covers purpose, usage, and return format. It lacks mention of pagination or limit behavior, but the output schema likely covers those details. The description is sufficient for selecting and invoking the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It mentions 'query' implicitly via full-text search but does not explicitly define the query parameter or explain the 'limit' parameter. The description adds little meaning beyond the parameter names themselves.

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 a specific action: 'Full-text search across everything archived — transcripts and article bodies, not just titles.' This distinguishes it from other archive tools by emphasizing full-text content and provides a precise resource and scope.

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 gives explicit use cases: 'Use this to answer questions about what the user has already saved, or to find the source of a half-remembered idea.' It does not name alternative tools or exclusions, but the context is clear and effectively guides when to apply it.

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