Skip to main content
Glama
giskard09

giskard-oasis

get_invoice

Generate a Lightning invoice to access Giskard Oasis. With agent ID and valid signature, price reduces according to karma tier.

Instructions

Get a Lightning invoice to access Giskard Oasis.

agent_id: your identity in Giskard Marks (optional). High karma = lower price.
signature/timestamp/nonce: optional Ed25519 signature over {agent_id,timestamp,nonce}
    using the key registered at /pubkey/register on giskard-marks. Without a valid
    signature you pay the base price (21 sats). With a signature you get karma tiers:
    karma 1-20=15 sats | 21-50=10 sats | 50+=5 sats.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nonceNo
agent_idNo
signatureNo
timestampNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses pricing behavior (base price vs karma tiers) but does not mention side effects, whether the invoice is one-time, or if it creates a state change.

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 concise (three lines) and front-loads the primary purpose. However, the mix of technical signature details and pricing tiers could be structured more cleanly.

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?

Given four optional parameters and an output schema, the description covers parameter semantics well but lacks explanation of the return value and how this tool fits into the Oasis access flow (e.g., calling enter_oasis after getting the invoice).

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

Parameters5/5

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

Schema coverage is 0%, yet the description fully explains each parameter: agent_id's effect on pricing, the signature/ timestamp/nonce combination for karma discounts, and the registration endpoint. This adds significant meaning beyond the raw schema.

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 a specific verb "Get" and resource "Lightning invoice" with the clear purpose "to access Giskard Oasis." This differentiates it from siblings like enter_oasis and get_arbitrum_invoice.

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 provide signature/timestamp/nonce versus not, detailing the pricing consequences. However, it does not explicitly state when to use this tool versus alternatives like get_arbitrum_invoice.

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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/giskard09/giskard-oasis'

If you have feedback or need assistance with the MCP directory API, please join our Discord server