Skip to main content
Glama
arbadacarbaYK

gittr-mcp

by arbadacarbaYK
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
JavaScript
Remote

announceSoftwareFromForgeRelease

Turn a forge release binary into a Nostr app announcement (NIP-82) with optional Blossom pinning.

Instructions

Announce software to Zapstore/NIP-82 (kinds 32267/30063/3063) from a forge Release binary. Same as gittr Nostr Apps (latest tag) or Releases → Announce on Nostr (tag=). Never a tagless app. Optional pinToBlossom streams files to primal/ditto/haven (never blossom.gittr.space). Auto-loads .nostr-keys.json if privkey omitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNoRelease tag to announce (omit = latest, same as Code sidebar)
appIdNoPackage id (e.g. com.example.app). Default: space.gittr.<repo>
relaysNo
topicsNoOptional extra t tags
appNameNoDisplay name (default: forge repo name)
licenseNoOptional SPDX license id
privkeyNonsec or hex (optional if .nostr-keys.json loaded)
summaryNoShort summary (max ~280 chars)
sourceUrlYesForge repository HTTPS URL with a Release that has an announceable binary
ownerPubkeyNoMust match signer (default: derived from privkey)
nip34AddressNoOptional NIP-34 pointer 30617:<owner-hex>:<repo>
pinToBlossomNoOptional: pin hashed files to public Blossom (primal/ditto/haven). Pin failure still announces the forge URL.
selectedApkUrlNoAlias of selectedAssetUrl (legacy)
selectedAssetUrlNoPrefer a specific hashed download URL from the release
includeSiblingAssetsNoPublish extra NIP-82 MIME files on the same tag (default true; skips extra APKs)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.0.6
    • addedInput schema / properties / includeSiblingAssets
      Added value: +{
+  "description": "Publish extra NIP-82 MIME files on the same tag (default true; skips extra APKs)",
+  "type": "boolean"
+}
    • addedInput schema / properties / pinToBlossom
      Added value: +{
+  "description": "Optional: pin hashed files to public Blossom (primal/ditto/haven). Pin failure still announces the forge URL.",
+  "type": "boolean"
+}
    • changedInput schema / properties / selectedApkUrl / description
      Previous value: -"Prefer a specific APK download URL from the release"New value: +"Alias of selectedAssetUrl (legacy)"
    • addedInput schema / properties / selectedAssetUrl
      Added value: +{
+  "description": "Prefer a specific hashed download URL from the release",
+  "type": "string"
+}
    • changedInput schema / properties / sourceUrl / description
      Previous value: -"Forge repository HTTPS URL with a Release that has an .apk"New value: +"Forge repository HTTPS URL with a Release that has an announceable binary"
    • addedInput schema / properties / tag
      Added value: +{
+  "description": "Release tag to announce (omit = latest, same as Code sidebar)",
+  "type": "string"
+}
  2. First observedv1.0.3

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it delivers meaningful traits: 'Auto-loads .nostr-keys.json if privkey omitted' covers auth needs, and 'pinToBlossom streams files to primal/ditto/haven (never blossom.gittr.space)' discloses destination behavior including an explicit exclusion. It does not cover failure modes or side effects on existing announcements, but the key behavioral traits are surfaced.

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?

Three dense sentences with zero filler: the core purpose is front-loaded in sentence one, usage analogies and the tagless constraint in sentence two, and optional behaviors (pinToBlossom, key auto-load) in sentence three. Every sentence earns its place and the most critical routing information appears first.

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?

For a complex 15-parameter tool with no output schema and no annotations, the description covers purpose, usage context, constraints, auth behavior, and pin destinations, and the 93% schema coverage fills in defaults and failure semantics (e.g., 'Pin failure still announces the forge URL'). It falls short only in not describing the expected return value/output and not explicitly naming the sibling tool for the tagless case.

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 high at 93%, so the baseline of 3 applies and the schema already documents most parameters. The description adds some contextual value beyond the schema—'pinToBlossom streams files to primal/ditto/haven (never blossom.gittr.space)' clarifies semantics and privkey auto-loading behavior is reinforced—but this is incremental rather than substantial.

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: 'Announce software to Zapstore/NIP-82 (kinds 32267/30063/3063) from a forge Release binary.' It distinguishes itself from related tools by declaring 'Never a tagless app' and referencing gittr UI equivalents, so an agent can separate it from publishSoftwareAnnounce and publishRepoAnnouncement without inspecting the schema.

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?

The description gives clear context for when to use the tool: 'Same as gittr Nostr Apps (latest tag) or Releases → Announce on Nostr (tag=)' and explicitly states the when-not condition 'Never a tagless app.' However, it points to UI analogues rather than naming sibling tools (e.g., publishSoftwareAnnounce) as the alternative for tagless cases, so the exclusion routing is slightly indirect.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools