giskard-search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PHOENIXD_URL | No | The URL of the phoenixd server (e.g., http://host.docker.internal:9740) | |
| OWNER_PRIVATE_KEY | No | Your Arbitrum private key for on-chain payment verification | |
| PHOENIXD_PASSWORD | Yes | The password for the phoenixd server |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_invoiceA | Get a Lightning invoice to pay before searching. |
| get_arbitrum_invoiceA | Get payment info to pay with ETH on Arbitrum instead of Lightning. |
| search_webC | Search the web. Pay with Lightning (payment_hash) or Arbitrum ETH (tx_hash). |
| search_newsB | Search recent news. Pay with Lightning (payment_hash) or Arbitrum ETH (tx_hash). |
| reportA | Report whether the search was useful. Helps Giskard improve. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool serves a clearly distinct purpose: payment via two methods, two search scopes, and feedback. No overlap or ambiguity.
All tools use snake_case and follow a consistent verb_noun pattern (e.g., get_invoice, search_web). The naming is predictable and uniform.
With 5 tools, the set is well-scoped for a paid search service. It covers essential actions without being over- or under-engineered.
The tool surface covers payment, search, and feedback comprehensively. A minor gap is the lack of a dedicated tool to view karma or pricing tiers, but it doesn't hinder core functionality.