Skip to main content
Glama
Sign In
terminal-love-mcp

terminal-love-mcp

by jpoindexter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Sync terminal tool catalog

sync_catalog

Syncs the Terminal Trove catalog to a local index for offline search, returning tool count, timestamp, and a 10-item sample. Force a rebuild with force=true.

Instructions

Fetches the full Terminal Trove catalog from sitemap + /list/ and builds a local index for fast offline search. Returns the tool count, build timestamp, and a 10-item sample. Pass force=true to force a rebuild even if the index is fresh.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sync_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoForce a full rebuild even if a fresh index is cached (default false)

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?

With no annotations, the description carries full burden. It discloses the fetching mechanism (sitemap + /list/), indexing, return values (tool count, timestamp, sample), and the force parameter's effect (rebuild even if fresh). Side effects like writing a local index are implied but not explicitly stated.

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 sentences long, front-loaded with the core action, and every sentence provides necessary 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?

Given the tool's simplicity (one optional parameter, no output schema), the description is fully complete: it explains input, behavior, and output clearly.

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 baseline is 3. The description adds explanatory context for the force parameter ('rebuild even if index is fresh'), which adds marginal value beyond the schema's description.

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 it fetches the full catalog and builds a local index, using specific verbs and resources. It distinguishes itself from sibling tools which focus on browsing, searching, or individual tool details.

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

Usage Guidelines3/5

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

The description implies usage for offline search but does not explicitly state when to use this tool over alternatives, nor does it provide exclusions or name alternative tools. The context is clear but lacks directive guidance.

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