Skip to main content
Glama
Sign In
gittr-mcp

gittr-mcp

by arbadacarbaYK
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

listWatchedRepos

Retrieve the list of repositories a user follows from their latest followed-repos event on Nostr relays by providing a pubkey and relays.

Instructions

List repos from your latest kind 10018 followed-repos event on relays

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": "listWatchedRepos"
  }
}

Input Schema

NameRequiredDescriptionDefault
pubkeyNo
relaysNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.5/5.0
Behavior3/5

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

There are no annotations, so the description carries full disclosure burden. It does add meaningful context that the data comes from the 'latest kind 10018 followed-repos event' on relays rather than a live repository list, but it omits details like error behavior, default relay handling, and return format.

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 a single, front-loaded sentence with no filler words. It efficiently communicates the action and the data source without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations, no output schema, and only a minimal description, the tool lacks crucial context like expected output shape, whether pubkey is required, what happens if no followed-repos event exists, and how relays are used. This makes it incomplete for an agent to invoke confidently.

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?

The schema has 0% description coverage and no per-parameter documentation. The description only vaguely hints at 'your' (suggesting pubkey) and 'on relays' (suggesting the relays array), but it does not explicitly explain the semantics or required format of either parameter.

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 uses 'List' plus a specific resource ('repos from your latest kind 10018 followed-repos event on relays'), clearly identifying what the tool does. It also distinguishes itself from siblings like listRepos and myRepos by referencing the Nostr event type.

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 when to use the tool (when you want repos from a user's latest followed-repos event), but it does not explicitly state when to prefer this over alternatives such as listRepos or listStars. No exclusionary guidance is provided.

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