Skip to main content
Glama
giskard09

ARGENTUM

by giskard09
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
submit_actionB

Submit a good action to ARGENTUM for community verification.

entity_id: your unique identifier (e.g. GitHub username)
entity_name: display name
entity_type: 'human' or 'agent'
action_type: HELP | BUILD | TEACH | FIX | WITNESS | CONNECT | RELEASE
description: what you did
proof: URL to evidence (GitHub PR, commit, etc.)
attest_actionA

Attest (verify) someone else's action. Your karma weight counts toward verification.

action_id: the action to attest
attester_id: your identifier
attester_name: your display name
note: optional comment
get_karmaB

Check an entity's karma, verified actions, and attestations given.

entity_id: the entity to look up
get_action_detailB

Get details of a specific action including attestations.

action_id: the action to look up
register_trailA

Register a Mycelium Trail — a verifiable recipe of MCP service calls.

author_id: your unique identifier
author_name: your display name
name: short trail name
description: what the trail does
steps_json: JSON list of steps, each {"service": "...", "tool": "...", "note": "..."}
price_sats: cost in sats per execution
list_trailsA

List Mycelium Trails available for execution.

sort: reputation | popular | recent | rating
limit: how many to show (default 20, max 50)
get_trailC

Get details of a Mycelium Trail including its step sequence.

trail_id: the trail id
execute_trailA

Record execution of a Mycelium Trail. The executor self-attests success or failure.

trail_id: the trail being executed
executor_id: your unique identifier
executor_name: your display name
status: 'success' or 'fail'
output_hash: optional sha256 of the output
payment_hash: optional Lightning payment hash
rate_trailB

Rate a Trail execution 1..5. Cannot rate own trail.

trail_id: the trail
execution_id: the execution to rate
rating: 1..5
get_leaderboardA

Get the karma leaderboard — top entities by reputation.

top: how many to show (default 10)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
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

TDQS

A3.5/5.0

Scored across 10 tools

Disambiguation4/5

The tools are divided into two clear clusters: karma/action verification and trail lifecycle. Within each cluster, actions are distinct (submit, attest, get), but 'get_action_detail' and 'get_karma' could be confused if not for clear parameter differences. 'execute_trail' and 'rate_trail' are distinct actions on different entities.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (submit_action, attest_action, get_karma, register_trail, list_trails, get_trail, execute_trail, rate_trail, get_leaderboard). No deviations or mixed conventions.

Tool Count5/5

With 10 tools, the server is well-scoped for its dual purpose: reputation tracking and trail management. Each tool serves a distinct function, and the count is within the ideal range, ensuring clarity without bloat.

Completeness4/5

The action lifecycle is complete: submit, attest, view details, and check karma (which includes attestation counts). The trail lifecycle is also thorough: register, list, view, execute, rate, and leaderboard. Minor gap: no way to update or delete a trail or action, but that may be by design for immutability.

Maintenance

ActivityActive
ResponsivenessResponsive

Resources