Skip to main content
Glama
Sign In

freeport-nostr

by io.github.ptrinh
OverviewDiscussionsAdmin

nostr_profile

Fetch NIP-01 profile metadata (kind 0) for one or more pubkeys — name, about, picture, nip05, lud16, etc. Optionally include each author's most recent notes (kind 1). General-purpose: works for any Nostr user, not just Freeport.

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": {
      "pubkeys": "<pubkeys>"
    },
    "name": "nostr_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
relaysNoOverride the relay set for this call (ws/wss URLs, max 10). Defaults to the server relays.
pubkeysYesHex pubkeys to fetch profiles for.
recentNotesNoIf >0, also fetch up to this many recent text notes (kind 1) per pubkey.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the event kinds (0 and optionally 1) and data fields, but does not mention error handling, relay behavior, or authentication needs. Adequate but minimal.

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?

Two sentences efficiently front-load the main purpose and scope, with no wasted words or redundancy.

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 simple fetch tool, the description covers the primary functionality and return values, but lacks details on error states or relay handling. Output schema is not provided, but return fields are listed.

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 100%. Description adds context by elaborating that pubkeys are for profile metadata and that recentNotes fetches kind 1 text notes, slightly increasing meaning beyond the schema descriptions.

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?

Description clearly states the tool fetches NIP-01 profile metadata (kind 0) for one or more pubkeys, including specific fields. It distinguishes from siblings by mentioning it's general-purpose and not limited to Freeport.

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?

Description implies usage for any Nostr user but does not provide explicit guidance on when to use this tool versus alternatives like nostr_get_event or nostr_query_raw. No when-not or exclusions.

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