Skip to main content
Glama

freeport-nostr

by io.github.ptrinh
OverviewDiscussionsAdmin

freeport_create_post

Publish a Freeport intent — an OFFER (side "offer": driver/provider/seller) or a REQUEST (side "request": rider/buyer). Provide EITHER a secretKey (nsec or hex — the server builds, signs and publishes; use a DEDICATED agent key, never a personal one — it is used once and never stored) OR a pre-signed event (you sign locally; nothing secret reaches the server). Strict rate limits apply. Returns the published event id + addressable d.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dNoStable id to republish/replace an existing post; defaults to random.
sideNooffer = provider/seller/driver; request = buyer/rider.
eventNoA complete, signed Nostr event (kind 32101/32102). Use instead of secretKey to keep keys off the server.
titleNo
marketNoMarket key, e.g. "rideshare" or "service".
relaysNo
schemaNoPayload schema, e.g. "rideshare/1" or "service/1".
topicsNoTopic `t` tags (area/category), e.g. ["vn_hanoi","vn_hanoi_ridesharing"].
windowNo
payloadNoIntent payload (from/to/location, payment, etc.) per the freeport://protocol resource.
geohashesNoGeohashes for location-scoped discovery. Each is expanded into all its prefixes (precision 1-6) so radius searches at any precision match.
secretKeyNonsec or 64-hex private key. Used transiently to sign; never stored. Omit if passing a pre-signed `event`.
expiresInMinutesNoHow long the post stays live (default 720). Max 30 days.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / geohashes / description
      Previous value: -"Geohash tags for location-scoped discovery."New value: +"Geohashes for location-scoped discovery. Each is expanded into all its prefixes (precision 1-6) so radius searches at any precision match."
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

No annotations provided, so description carries full burden. It discloses transient key usage, return value (event id + d), and rate limits. It implies overwrite behavior via 'd' parameter but does not explicitly state side effects or authorization needs. Adequate but not fully exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single paragraph with clear flow: purpose, auth methods, rate limits, return. All sentences add value. Could be slightly shorter but efficient.

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

Completeness3/5

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

With 13 parameters, nested objects, and no output schema, the description is moderately complete. It explains return format and rate limits, but does not cover error handling, detailed behavior of window/payload, or idempotency. Adequate but leaves some gaps.

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

Parameters4/5

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

Schema coverage is 77%, so baseline is 3. The description adds value beyond schema by explaining purpose of secretKey, event, side, and d. It clarifies the side enum and transient nature of secretKey. Some parameters (window, payload) are only in schema, but overall helpful.

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 the tool publishes a Freeport intent, distinguishing between OFFER and REQUEST. It uses specific verbs ('Publish') and resource ('Freeport intent'), and is distinct from sibling tools which are read/search operations.

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 explains when to use secretKey vs pre-signed event, mentions strict rate limits, and advises using dedicated keys. However, it lacks explicit when-not-to-use or alternative tool comparisons, though siblings are all read-oriented so no direct competition.

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

All freeport-nostr toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources