Skip to content

Instantly share code, notes, and snippets.

@lewtun

lewtun/mcp-bench-sample-prompt.txt

Created September 6, 2025 10:21
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save lewtun/8deff6e9c6f22187ff75141c4f5703ef to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save lewtun/8deff6e9c6f22187ff75141c4f5703ef to your computer and use it in GitHub Desktop.
Download ZIP
MCP-Bench Sample Prompt
Raw
mcp-bench-sample-prompt.txt
<|im_start|>system
You are a strategic multi-tool AI agent planner for Round 1. Plan parallel execution of independent tools for this round.<|im_end|>
<|im_start|>user
You are a strategic decision-making expert for a multi-tool AI agent using the provided tools to perform the task.
TASK: "Hey, I’m working on this new dashboard that pulls search results from three different services—one for AI stuff, one for code hosting, and one for edge networking—and I’m scratching my head over how each handles pagination. Some APIs might use a page/page_size setup, others a cursor or next_cursor, and I’m not even sure if all of them support paging in their search calls or if I have to switch to their “list” routes instead.
Could you dig into each service’s search endpoints and tell me:
• whether it pages at all or not
• if it does, what style it uses (page numbers, cursors, etc.)
• the exact parameter names, types, required flags, and defaults
• any response fields that indicate where to pick up the next batch
And if a service’s search doesn’t page, check its list endpoints the same way. I really need a solid breakdown—names, defaults, response tokens—the whole picture, so I can convince my boss this setup will actually work. Need real details, not guesses. Thanks!"
CURRENT ROUND: 1
AVAILABLE TOOLS ACROSS SERVERS:
Tool: `OpenAPI Explorer:getApiOverview` (Server: OpenAPI Explorer)
Description: Get an overview of an OpenAPI specification. This should be the first step when working with any API.
- openai - OpenAI is a large AI service provider providing state of the art models in various modalities.
- github - GitHub is where one hosts their code in a central location, to collaborate with others
- socialdata.tools
- podscan.fm - Search through podcast transcripts, get alerts
- x - Official Twitter/X API
- cloudflare - Cloudflare provides content delivery network services, cloud cybersecurity, DDoS mitigation, wide area network services, Domain Name Service, and ICANN-accredited domain registration services
- npm-registry
- supabase - Create hosted Postgres Databases with API
- hackernews - Readonly API for posts, comments, and profiles from news.ycombinator.com
- stripe - Create a paywall for your app or invoices
- slack - A very common app used for communication at work
- vercel - Vercel is a cloud hosting solution for full stack applications
- val-town - Host serverless APIs
- firecrawl - API for interacting with Firecrawl services to perform web scraping and crawling tasks.
- playht - The PlayHT's API API allows developers to Realtime Text to Speech streaming Stream audio bytes from text, Convert long form Text to Speech Generate audio from text, and Voice Cloning Instant Cloning.
- serper - The worlds fastest and cheapest google search api
- replicate
- brandwatch - Watch social media about your brand
- jina-reader - Read webpages in markdown, html, or screenshot
- upstash-redis - Control a Redis database over API
- upstash-qstash - Scheduling and batching API calls
- upstash-vector - Control a Vector database over API
- digitalocean
- apisguru - Public API to find OpenAPIs on https://apis.guru
- groq - Cloud AI Provider with multiple transformer LLMs and other modalities, with very fast inference
- notion-dbs - Notion Databases API
- posthog-capture-api - Posthog is a Product analytics platform allowing companies to track and understand their users
- google-analytics4 - The Google Analytics Admin API allows for programmatic access to the Google Analytics 4 (GA4) configuration data and is only compatible with GA4 properties
- google-analytics3 - Views and manages your Google Analytics data (GA3)
- anthropic-message-api
- probo-nl
- whatsapp-business - The WhatsApp Business Platform gives medium to large businesses the ability to connect with customers at scale. You can start WhatsApp conversations with your customers in minutes, send them care notifications or purchase updates, offer personalized services, and provide support in the channel that your customers prefer.
- shopify - Shopify Admin API
- twilio-messaging
- huggingface
- doppio
- multion
- browserless - Web browsing API
- bol-com-retailer - Dutch shopping platform
- statusbrew - Social media planning API for facebook, instagram, twitter, linkedin, google my business, pinterest, youtube, and tiktok.
- swagger-validator - Validators for swagger 2.0 and 3.x specifications of OpenAPIs
- google-mail - Manage GMail
- youtube-data - The YouTube Data API v3 is an API that provides access to YouTube data, such as videos, playlists, and channels.
- google-sheets
- google-drive
- google-secret-manager
- flyio
- vapi
- klippa
- uberduck
- twilio
- saltedge - Bank integrations
- google-search-console
- aws-cloudwatch-insights
- aws-cloudfront
- aws-email
- aws-s3-control
- aws-s3
- aws-sagemaker
- aws-sagemaker-edge
- aws-sagemaker-featureStore
- bunq
- hootsuite
- robocorp
- sendgrid
- google-calendar
- google-docs
Input Schema:
```json
{
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "API identifier, can be a known ID from openapisearch.com or a URL leading to a raw OpenAPI file"
}
},
"required": [
"id"
]
}
```
Tool: `OpenAPI Explorer:getApiOperation` (Server: OpenAPI Explorer)
Description: Get details about a specific operation from an OpenAPI specification. Use this after getting an overview.
- openai - OpenAI is a large AI service provider providing state of the art models in various modalities.
- github - GitHub is where one hosts their code in a central location, to collaborate with others
- socialdata.tools
- podscan.fm - Search through podcast transcripts, get alerts
- x - Official Twitter/X API
- cloudflare - Cloudflare provides content delivery network services, cloud cybersecurity, DDoS mitigation, wide area network services, Domain Name Service, and ICANN-accredited domain registration services
- npm-registry
- supabase - Create hosted Postgres Databases with API
- hackernews - Readonly API for posts, comments, and profiles from news.ycombinator.com
- stripe - Create a paywall for your app or invoices
- slack - A very common app used for communication at work
- vercel - Vercel is a cloud hosting solution for full stack applications
- val-town - Host serverless APIs
- firecrawl - API for interacting with Firecrawl services to perform web scraping and crawling tasks.
- playht - The PlayHT's API API allows developers to Realtime Text to Speech streaming Stream audio bytes from text, Convert long form Text to Speech Generate audio from text, and Voice Cloning Instant Cloning.
- serper - The worlds fastest and cheapest google search api
- replicate
- brandwatch - Watch social media about your brand
- jina-reader - Read webpages in markdown, html, or screenshot
- upstash-redis - Control a Redis database over API
- upstash-qstash - Scheduling and batching API calls
- upstash-vector - Control a Vector database over API
- digitalocean
- apisguru - Public API to find OpenAPIs on https://apis.guru
- groq - Cloud AI Provider with multiple transformer LLMs and other modalities, with very fast inference
- notion-dbs - Notion Databases API
- posthog-capture-api - Posthog is a Product analytics platform allowing companies to track and understand their users
- google-analytics4 - The Google Analytics Admin API allows for programmatic access to the Google Analytics 4 (GA4) configuration data and is only compatible with GA4 properties
- google-analytics3 - Views and manages your Google Analytics data (GA3)
- anthropic-message-api
- probo-nl
- whatsapp-business - The WhatsApp Business Platform gives medium to large businesses the ability to connect with customers at scale. You can start WhatsApp conversations with your customers in minutes, send them care notifications or purchase updates, offer personalized services, and provide support in the channel that your customers prefer.
- shopify - Shopify Admin API
- twilio-messaging
- huggingface
- doppio
- multion
- browserless - Web browsing API
- bol-com-retailer - Dutch shopping platform
- statusbrew - Social media planning API for facebook, instagram, twitter, linkedin, google my business, pinterest, youtube, and tiktok.
- swagger-validator - Validators for swagger 2.0 and 3.x specifications of OpenAPIs
- google-mail - Manage GMail
- youtube-data - The YouTube Data API v3 is an API that provides access to YouTube data, such as videos, playlists, and channels.
- google-sheets
- google-drive
- google-secret-manager
- flyio
- vapi
- klippa
- uberduck
- twilio
- saltedge - Bank integrations
- google-search-console
- aws-cloudwatch-insights
- aws-cloudfront
- aws-email
- aws-s3-control
- aws-s3
- aws-sagemaker
- aws-sagemaker-edge
- aws-sagemaker-featureStore
- bunq
- hootsuite
- robocorp
- sendgrid
- google-calendar
- google-docs
Input Schema:
```json
{
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "API identifier, can be a known ID from openapisearch.com or a URL leading to a raw OpenAPI file"
},
"operationIdOrRoute": {
"type": "string",
"description": "Operation ID or route path to retrieve"
}
},
"required": [
"id",
"operationIdOrRoute"
]
}
```
Tool: `Time MCP:get_current_time` (Server: Time MCP)
Description: Get current time in a specific timezones
Input Schema:
```json
{
"type": "object",
"properties": {
"timezone": {
"type": "string",
"description": "IANA timezone name (e.g., 'America/New_York', 'Europe/London'). Use 'Etc/UTC' as local timezone if no timezone provided by the user."
}
},
"required": [
"timezone"
]
}
```
Tool: `Time MCP:convert_time` (Server: Time MCP)
Description: Convert time between timezones
Input Schema:
```json
{
"type": "object",
"properties": {
"source_timezone": {
"type": "string",
"description": "Source IANA timezone name (e.g., 'America/New_York', 'Europe/London'). Use 'Etc/UTC' as local timezone if no source timezone provided by the user."
},
"time": {
"type": "string",
"description": "Time to convert in 24-hour format (HH:MM)"
},
"target_timezone": {
"type": "string",
"description": "Target IANA timezone name (e.g., 'Asia/Tokyo', 'America/San_Francisco'). Use 'Etc/UTC' as local timezone if no target timezone provided by the user."
}
},
"required": [
"source_timezone",
"time",
"target_timezone"
]
}
```
Tool: `Bibliomantic:i_ching_divination` (Server: Bibliomantic)
Description:
Enhanced I Ching divination with traditional three-coin method and changing lines.
MAINTAINS EXACT BACKWARD COMPATIBILITY while providing richer content.
Input Schema:
```json
{
"properties": {
"query": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"title": "Query"
}
},
"title": "i_ching_divinationArguments",
"type": "object"
}
```
Tool: `Bibliomantic:bibliomantic_consultation` (Server: Bibliomantic)
Description:
Enhanced bibliomantic consultation with full traditional I Ching elements.
DRAMATICALLY IMPROVED CONTENT while maintaining exact interface compatibility.
Input Schema:
```json
{
"properties": {
"query": {
"title": "Query",
"type": "string"
}
},
"required": [
"query"
],
"title": "bibliomantic_consultationArguments",
"type": "object"
}
```
Tool: `Bibliomantic:get_hexagram_details` (Server: Bibliomantic)
Description:
Enhanced hexagram details with traditional Chinese names, Unicode symbols, and rich commentary.
MAINTAINS BACKWARD COMPATIBILITY while dramatically improving content quality.
Input Schema:
```json
{
"properties": {
"hexagram_number": {
"title": "Hexagram Number",
"type": "integer"
}
},
"required": [
"hexagram_number"
],
"title": "get_hexagram_detailsArguments",
"type": "object"
}
```
Tool: `Bibliomantic:server_statistics` (Server: Bibliomantic)
Description: Enhanced server statistics
Input Schema:
```json
{
"properties": {},
"title": "server_statisticsArguments",
"type": "object"
}
```
Tool: `Call for Papers:get_events` (Server: Call for Papers)
Description: Search for conferences matching specific keywords.
Input Schema:
```json
{
"properties": {
"keywords": {
"title": "Keywords",
"type": "string"
},
"limit": {
"default": 10,
"title": "Limit",
"type": "integer"
}
},
"required": [
"keywords"
],
"title": "get_eventsArguments",
"type": "object"
}
```
Tool: `Context7:resolve-library-id` (Server: Context7)
Description: Resolves a package/product name to a Context7-compatible library ID and returns a list of matching libraries.
You MUST call this function before 'get-library-docs' to obtain a valid Context7-compatible library ID UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query.
Selection Process:
1. Analyze the query to understand what library/package the user is looking for
2. Return the most relevant match based on:
- Name similarity to the query (exact matches prioritized)
- Description relevance to the query's intent
- Documentation coverage (prioritize libraries with higher Code Snippet counts)
- Trust score (consider libraries with scores of 7-10 more authoritative)
Response Format:
- Return the selected library ID in a clearly marked section
- Provide a brief explanation for why this library was chosen
- If multiple good matches exist, acknowledge this but proceed with the most relevant one
- If no good matches exist, clearly state this and suggest query refinements
For ambiguous queries, request clarification before proceeding with a best-guess match.
Input Schema:
```json
{
"type": "object",
"properties": {
"libraryName": {
"type": "string",
"description": "Library name to search for and retrieve a Context7-compatible library ID."
}
},
"required": [
"libraryName"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `Context7:get-library-docs` (Server: Context7)
Description: Fetches up-to-date documentation for a library. You must call 'resolve-library-id' first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query.
Input Schema:
```json
{
"type": "object",
"properties": {
"context7CompatibleLibraryID": {
"type": "string",
"description": "Exact Context7-compatible library ID (e.g., '/mongodb/docs', '/vercel/next.js', '/supabase/supabase', '/vercel/next.js/v14.3.0-canary.87') retrieved from 'resolve-library-id' or directly from user query in the format '/org/project' or '/org/project/version'."
},
"topic": {
"type": "string",
"description": "Topic to focus documentation on (e.g., 'hooks', 'routing')."
},
"tokens": {
"type": "number",
"description": "Maximum number of tokens of documentation to retrieve (default: 10000). Higher values provide more context but consume more tokens."
}
},
"required": [
"context7CompatibleLibraryID"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `DEX Paprika:getNetworks` (Server: DEX Paprika)
Description: REQUIRED FIRST STEP: Get all supported blockchain networks. Always call this first to see available networks before using any network-specific functions. Returns network IDs like "ethereum", "solana", etc.
Input Schema:
```json
{
"type": "object",
"properties": {},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `DEX Paprika:getNetworkDexes` (Server: DEX Paprika)
Description: Get available DEXes on a specific network. First call getNetworks to see valid network IDs.
Input Schema:
```json
{
"type": "object",
"properties": {
"network": {
"type": "string",
"description": "Network ID from getNetworks (e.g., \"ethereum\", \"solana\")"
},
"page": {
"type": "number",
"default": 0,
"description": "Page number for pagination"
},
"limit": {
"type": "number",
"default": 10,
"description": "Number of items per page"
}
},
"required": [
"network"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `DEX Paprika:getNetworkPools` (Server: DEX Paprika)
Description: PRIMARY POOL FUNCTION: Get top liquidity pools on a specific network. This is the MAIN way to get pool data - there is NO global pools function. Use this instead of any "getTopPools" or "getAllPools" concepts.
Input Schema:
```json
{
"type": "object",
"properties": {
"network": {
"type": "string",
"description": "Network ID from getNetworks (required) - e.g., \"ethereum\", \"solana\""
},
"page": {
"type": "number",
"default": 0,
"description": "Page number for pagination"
},
"limit": {
"type": "number",
"default": 10,
"description": "Number of items per page (max 100)"
},
"sort": {
"type": "string",
"enum": [
"asc",
"desc"
],
"default": "desc",
"description": "Sort order"
},
"orderBy": {
"type": "string",
"enum": [
"volume_usd",
"price_usd",
"transactions",
"last_price_change_usd_24h",
"created_at"
],
"default": "volume_usd",
"description": "Field to order by"
}
},
"required": [
"network"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `DEX Paprika:getDexPools` (Server: DEX Paprika)
Description: Get pools from a specific DEX on a network. First use getNetworks, then getNetworkDexes to find valid DEX IDs.
Input Schema:
```json
{
"type": "object",
"properties": {
"network": {
"type": "string",
"description": "Network ID from getNetworks (e.g., \"ethereum\", \"solana\")"
},
"dex": {
"type": "string",
"description": "DEX identifier from getNetworkDexes (e.g., \"uniswap_v3\")"
},
"page": {
"type": "number",
"default": 0,
"description": "Page number for pagination"
},
"limit": {
"type": "number",
"default": 10,
"description": "Number of items per page (max 100)"
},
"sort": {
"type": "string",
"enum": [
"asc",
"desc"
],
"default": "desc",
"description": "Sort order"
},
"orderBy": {
"type": "string",
"enum": [
"volume_usd",
"price_usd",
"transactions",
"last_price_change_usd_24h",
"created_at"
],
"default": "volume_usd",
"description": "Field to order by"
}
},
"required": [
"network",
"dex"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `DEX Paprika:getPoolDetails` (Server: DEX Paprika)
Description: Get detailed information about a specific pool. Requires network ID from getNetworks and a pool address.
Input Schema:
```json
{
"type": "object",
"properties": {
"network": {
"type": "string",
"description": "Network ID from getNetworks (e.g., \"ethereum\", \"solana\")"
},
"poolAddress": {
"type": "string",
"description": "Pool address or identifier"
},
"inversed": {
"type": "boolean",
"default": false,
"description": "Whether to invert the price ratio"
}
},
"required": [
"network",
"poolAddress"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `DEX Paprika:getTokenDetails` (Server: DEX Paprika)
Description: Get detailed information about a specific token on a network. First use getNetworks to get valid network IDs.
Input Schema:
```json
{
"type": "object",
"properties": {
"network": {
"type": "string",
"description": "Network ID from getNetworks (e.g., \"ethereum\", \"solana\")"
},
"tokenAddress": {
"type": "string",
"description": "Token address or identifier"
}
},
"required": [
"network",
"tokenAddress"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `DEX Paprika:getTokenPools` (Server: DEX Paprika)
Description: Get liquidity pools containing a specific token on a network. Great for finding where a token is traded.
Input Schema:
```json
{
"type": "object",
"properties": {
"network": {
"type": "string",
"description": "Network ID from getNetworks (e.g., \"ethereum\", \"solana\")"
},
"tokenAddress": {
"type": "string",
"description": "Token address or identifier"
},
"page": {
"type": "number",
"default": 0,
"description": "Page number for pagination"
},
"limit": {
"type": "number",
"default": 10,
"description": "Number of items per page (max 100)"
},
"sort": {
"type": "string",
"enum": [
"asc",
"desc"
],
"default": "desc",
"description": "Sort order"
},
"orderBy": {
"type": "string",
"enum": [
"volume_usd",
"price_usd",
"transactions",
"last_price_change_usd_24h",
"created_at"
],
"default": "volume_usd",
"description": "Field to order by"
},
"reorder": {
"type": "boolean",
"description": "If true, reorders the pool so that the specified token becomes the primary token for all metrics"
},
"address": {
"type": "string",
"description": "Filter pools that contain this additional token address"
}
},
"required": [
"network",
"tokenAddress"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `DEX Paprika:getPoolOHLCV` (Server: DEX Paprika)
Description: Get historical price data (OHLCV) for a pool - essential for price analysis, backtesting, and visualization. Requires network and pool address.
Input Schema:
```json
{
"type": "object",
"properties": {
"network": {
"type": "string",
"description": "Network ID from getNetworks (e.g., \"ethereum\", \"solana\")"
},
"poolAddress": {
"type": "string",
"description": "Pool address or identifier"
},
"start": {
"type": "string",
"description": "Start time for historical data (Unix timestamp, RFC3339 timestamp, or yyyy-mm-dd format)"
},
"end": {
"type": "string",
"description": "End time for historical data (max 1 year from start)"
},
"limit": {
"type": "number",
"default": 1,
"description": "Number of data points to retrieve (max 366) - adjust for different analysis needs"
},
"interval": {
"type": "string",
"default": "24h",
"description": "Interval granularity: 1m, 5m, 10m, 15m, 30m, 1h, 6h, 12h, 24h"
},
"inversed": {
"type": "boolean",
"default": false,
"description": "Whether to invert the price ratio for alternative pair perspective (e.g., ETH/USDC vs USDC/ETH)"
}
},
"required": [
"network",
"poolAddress",
"start"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `DEX Paprika:getPoolTransactions` (Server: DEX Paprika)
Description: Get recent transactions for a specific pool. Shows swaps, adds, removes. Requires network and pool address.
Input Schema:
```json
{
"type": "object",
"properties": {
"network": {
"type": "string",
"description": "Network ID from getNetworks (e.g., \"ethereum\", \"solana\")"
},
"poolAddress": {
"type": "string",
"description": "Pool address or identifier"
},
"page": {
"type": "number",
"default": 0,
"description": "Page number for pagination (up to 100 pages)"
},
"limit": {
"type": "number",
"default": 10,
"description": "Number of items per page (max 100)"
},
"cursor": {
"type": "string",
"description": "Transaction ID used for cursor-based pagination"
}
},
"required": [
"network",
"poolAddress"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `DEX Paprika:search` (Server: DEX Paprika)
Description: Search across ALL networks for tokens, pools, and DEXes by name, symbol, or address. Good starting point when you don't know the specific network.
Input Schema:
```json
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Search term (e.g., \"uniswap\", \"bitcoin\", or a token address)"
}
},
"required": [
"query"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `DEX Paprika:getStats` (Server: DEX Paprika)
Description: Get high-level statistics about the DexPaprika ecosystem: total networks, DEXes, pools, and tokens available.
Input Schema:
```json
{
"type": "object",
"properties": {},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `Hugging Face:search-models` (Server: Hugging Face)
Description: Search for models on Hugging Face Hub
Input Schema:
```json
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Search term (e.g., 'bert', 'gpt')"
},
"author": {
"type": "string",
"description": "Filter by author/organization (e.g., 'huggingface', 'google')"
},
"tags": {
"type": "string",
"description": "Filter by tags (e.g., 'text-classification', 'translation')"
},
"limit": {
"type": "integer",
"description": "Maximum number of results to return"
}
}
}
```
Tool: `Hugging Face:get-model-info` (Server: Hugging Face)
Description: Get detailed information about a specific model
Input Schema:
```json
{
"type": "object",
"properties": {
"model_id": {
"type": "string",
"description": "The ID of the model (e.g., 'google/bert-base-uncased')"
}
},
"required": [
"model_id"
]
}
```
Tool: `Hugging Face:search-datasets` (Server: Hugging Face)
Description: Search for datasets on Hugging Face Hub
Input Schema:
```json
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Search term"
},
"author": {
"type": "string",
"description": "Filter by author/organization"
},
"tags": {
"type": "string",
"description": "Filter by tags"
},
"limit": {
"type": "integer",
"description": "Maximum number of results to return"
}
}
}
```
Tool: `Hugging Face:get-dataset-info` (Server: Hugging Face)
Description: Get detailed information about a specific dataset
Input Schema:
```json
{
"type": "object",
"properties": {
"dataset_id": {
"type": "string",
"description": "The ID of the dataset (e.g., 'squad')"
}
},
"required": [
"dataset_id"
]
}
```
Tool: `Hugging Face:search-spaces` (Server: Hugging Face)
Description: Search for Spaces on Hugging Face Hub
Input Schema:
```json
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Search term"
},
"author": {
"type": "string",
"description": "Filter by author/organization"
},
"tags": {
"type": "string",
"description": "Filter by tags"
},
"sdk": {
"type": "string",
"description": "Filter by SDK (e.g., 'streamlit', 'gradio', 'docker')"
},
"limit": {
"type": "integer",
"description": "Maximum number of results to return"
}
}
}
```
Tool: `Hugging Face:get-space-info` (Server: Hugging Face)
Description: Get detailed information about a specific Space
Input Schema:
```json
{
"type": "object",
"properties": {
"space_id": {
"type": "string",
"description": "The ID of the Space (e.g., 'huggingface/diffusers-demo')"
}
},
"required": [
"space_id"
]
}
```
Tool: `Hugging Face:get-paper-info` (Server: Hugging Face)
Description: Get information about a specific paper on Hugging Face
Input Schema:
```json
{
"type": "object",
"properties": {
"arxiv_id": {
"type": "string",
"description": "The arXiv ID of the paper (e.g., '1810.04805')"
}
},
"required": [
"arxiv_id"
]
}
```
Tool: `Hugging Face:get-daily-papers` (Server: Hugging Face)
Description: Get the list of daily papers curated by Hugging Face
Input Schema:
```json
{
"type": "object",
"properties": {}
}
```
Tool: `Hugging Face:search-collections` (Server: Hugging Face)
Description: Search for collections on Hugging Face Hub
Input Schema:
```json
{
"type": "object",
"properties": {
"owner": {
"type": "string",
"description": "Filter by owner"
},
"item": {
"type": "string",
"description": "Filter by item (e.g., 'models/teknium/OpenHermes-2.5-Mistral-7B')"
},
"query": {
"type": "string",
"description": "Search term for titles and descriptions"
},
"limit": {
"type": "integer",
"description": "Maximum number of results to return"
}
}
}
```
Tool: `Hugging Face:get-collection-info` (Server: Hugging Face)
Description: Get detailed information about a specific collection
Input Schema:
```json
{
"type": "object",
"properties": {
"namespace": {
"type": "string",
"description": "The namespace of the collection (user or organization)"
},
"collection_id": {
"type": "string",
"description": "The ID part of the collection"
}
},
"required": [
"namespace",
"collection_id"
]
}
```
Tool: `Metropolitan Museum:list-departments` (Server: Metropolitan Museum)
Description: List all departments in the Metropolitan Museum of Art (Met Museum)
Input Schema:
```json
{
"type": "object",
"properties": {
"__intent": {
"type": "string",
"description": "In \u2264 30 words, describe why you are calling this tool and how its result advances your overall task. Don't use first-person pronouns like \"I\" or \"my\". Make sure to give a gist of the whole task and how this tool fits into it."
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"__intent"
]
}
```
Tool: `Metropolitan Museum:search-museum-objects` (Server: Metropolitan Museum)
Description: Search for objects in the Metropolitan Museum of Art (Met Museum). Will return Total objects found, followed by a list of Object Ids.The parameter title should be set to true if you want to search for objects by title.The parameter hasImages is false by default, but can be set to true to return objects without images.If the parameter hasImages is true, the parameter title should be false.
Input Schema:
```json
{
"type": "object",
"properties": {
"q": {
"type": "string",
"description": "The search query, Returns a listing of all Object IDs for objects that contain the search query within the object's data"
},
"hasImages": {
"type": "boolean",
"default": false,
"description": "Only returns objects that have images"
},
"title": {
"type": "boolean",
"default": false,
"description": "This should be set to true if you want to search for objects by title"
},
"departmentId": {
"type": "number",
"description": "Returns objects that are in the specified department. The departmentId should come from the 'list-departments' tool."
},
"__intent": {
"type": "string",
"description": "In \u2264 30 words, describe why you are calling this tool and how its result advances your overall task. Don't use first-person pronouns like \"I\" or \"my\". Make sure to give a gist of the whole task and how this tool fits into it."
}
},
"required": [
"q",
"__intent"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `Metropolitan Museum:get-museum-object` (Server: Metropolitan Museum)
Description: Get a museum object by its ID, from the Metropolitan Museum of Art Collection
Input Schema:
```json
{
"type": "object",
"properties": {
"objectId": {
"type": "number",
"description": "The ID of the museum object to retrieve"
},
"returnImage": {
"type": "boolean",
"default": true,
"description": "Whether to return the image (if available) of the object and add it to the server resources"
},
"__intent": {
"type": "string",
"description": "In \u2264 30 words, describe why you are calling this tool and how its result advances your overall task. Don't use first-person pronouns like \"I\" or \"my\". Make sure to give a gist of the whole task and how this tool fits into it."
}
},
"required": [
"objectId",
"__intent"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `NASA Data:get_astronomy_picture_of_day` (Server: NASA Data)
Description: Get NASA's astronomy picture of the day.
Args:
date: Date of the image in YYYY-MM-DD format. If not specified, the current date is used.
count: If specified, returns 'count' random images. Cannot be used with 'date'.
thumbs: If True, returns the thumbnail URL for videos. If APOD is not a video, this parameter is ignored.
Input Schema:
```json
{
"properties": {
"date": {
"default": null,
"title": "Date",
"type": "string"
},
"count": {
"default": null,
"title": "Count",
"type": "integer"
},
"thumbs": {
"default": false,
"title": "Thumbs",
"type": "boolean"
}
},
"title": "get_astronomy_picture_of_dayArguments",
"type": "object"
}
```
Tool: `NASA Data:get_asteroids_feed` (Server: NASA Data)
Description: Get a list of asteroids based on their closest approach date to Earth.
Args:
start_date: Start date for asteroid search in YYYY-MM-DD format.
end_date: End date for asteroid search in YYYY-MM-DD format.
The Feed date limit is only 7 Days. If not specified, 7 days after start_date is used.
Input Schema:
```json
{
"properties": {
"start_date": {
"title": "Start Date",
"type": "string"
},
"end_date": {
"default": null,
"title": "End Date",
"type": "string"
}
},
"required": [
"start_date"
],
"title": "get_asteroids_feedArguments",
"type": "object"
}
```
Tool: `NASA Data:get_asteroid_lookup` (Server: NASA Data)
Description: Look up a specific asteroid based on its NASA JPL ID.
Args:
asteroid_id: Asteroid ID in the NASA JPL small body (SPK-ID) system.
Input Schema:
```json
{
"properties": {
"asteroid_id": {
"title": "Asteroid Id",
"type": "string"
}
},
"required": [
"asteroid_id"
],
"title": "get_asteroid_lookupArguments",
"type": "object"
}
```
Tool: `NASA Data:browse_asteroids` (Server: NASA Data)
Description: Browse the asteroid dataset.
Input Schema:
```json
{
"properties": {},
"title": "browse_asteroidsArguments",
"type": "object"
}
```
Tool: `NASA Data:get_coronal_mass_ejection` (Server: NASA Data)
Description: Get coronal mass ejection (CME) data.
Args:
start_date: Start date in YYYY-MM-DD format. Defaults to 30 days before current date.
end_date: End date in YYYY-MM-DD format. Defaults to current date.
Input Schema:
```json
{
"properties": {
"start_date": {
"default": null,
"title": "Start Date",
"type": "string"
},
"end_date": {
"default": null,
"title": "End Date",
"type": "string"
}
},
"title": "get_coronal_mass_ejectionArguments",
"type": "object"
}
```
Tool: `NASA Data:get_geomagnetic_storm` (Server: NASA Data)
Description: Get geomagnetic storm (GST) data.
Args:
start_date: Start date in YYYY-MM-DD format. Defaults to 30 days before current date.
end_date: End date in YYYY-MM-DD format. Defaults to current date.
Input Schema:
```json
{
"properties": {
"start_date": {
"default": null,
"title": "Start Date",
"type": "string"
},
"end_date": {
"default": null,
"title": "End Date",
"type": "string"
}
},
"title": "get_geomagnetic_stormArguments",
"type": "object"
}
```
Tool: `NASA Data:get_solar_flare` (Server: NASA Data)
Description: Get solar flare (FLR) data.
Args:
start_date: Start date in YYYY-MM-DD format. Defaults to 30 days before current date.
end_date: End date in YYYY-MM-DD format. Defaults to current date.
Input Schema:
```json
{
"properties": {
"start_date": {
"default": null,
"title": "Start Date",
"type": "string"
},
"end_date": {
"default": null,
"title": "End Date",
"type": "string"
}
},
"title": "get_solar_flareArguments",
"type": "object"
}
```
Tool: `NASA Data:get_solar_energetic_particle` (Server: NASA Data)
Description: Get solar energetic particle (SEP) data.
Args:
start_date: Start date in YYYY-MM-DD format. Defaults to 30 days before current date.
end_date: End date in YYYY-MM-DD format. Defaults to current date.
Input Schema:
```json
{
"properties": {
"start_date": {
"default": null,
"title": "Start Date",
"type": "string"
},
"end_date": {
"default": null,
"title": "End Date",
"type": "string"
}
},
"title": "get_solar_energetic_particleArguments",
"type": "object"
}
```
Tool: `NASA Data:get_magnetopause_crossing` (Server: NASA Data)
Description: Get magnetopause crossing (MPC) data.
Args:
start_date: Start date in YYYY-MM-DD format. Defaults to 30 days before current date.
end_date: End date in YYYY-MM-DD format. Defaults to current date.
Input Schema:
```json
{
"properties": {
"start_date": {
"default": null,
"title": "Start Date",
"type": "string"
},
"end_date": {
"default": null,
"title": "End Date",
"type": "string"
}
},
"title": "get_magnetopause_crossingArguments",
"type": "object"
}
```
Tool: `NASA Data:get_radiation_belt_enhancement` (Server: NASA Data)
Description: Get radiation belt enhancement (RBE) data.
Args:
start_date: Start date in YYYY-MM-DD format. Defaults to 30 days before current date.
end_date: End date in YYYY-MM-DD format. Defaults to current date.
Input Schema:
```json
{
"properties": {
"start_date": {
"default": null,
"title": "Start Date",
"type": "string"
},
"end_date": {
"default": null,
"title": "End Date",
"type": "string"
}
},
"title": "get_radiation_belt_enhancementArguments",
"type": "object"
}
```
Tool: `NASA Data:get_hight_speed_stream` (Server: NASA Data)
Description: Get high speed stream (HSS) data.
Args:
start_date: Start date in YYYY-MM-DD format. Defaults to 30 days before current date.
end_date: End date in YYYY-MM-DD format. Defaults to current date.
Input Schema:
```json
{
"properties": {
"start_date": {
"default": null,
"title": "Start Date",
"type": "string"
},
"end_date": {
"default": null,
"title": "End Date",
"type": "string"
}
},
"title": "get_hight_speed_streamArguments",
"type": "object"
}
```
Tool: `NASA Data:get_wsa_enlil_simulation` (Server: NASA Data)
Description: Get WSA+Enlil simulation data.
Args:
start_date: Start date in YYYY-MM-DD format. Defaults to 7 days before current date.
end_date: End date in YYYY-MM-DD format. Defaults to current date.
Input Schema:
```json
{
"properties": {
"start_date": {
"default": null,
"title": "Start Date",
"type": "string"
},
"end_date": {
"default": null,
"title": "End Date",
"type": "string"
}
},
"title": "get_wsa_enlil_simulationArguments",
"type": "object"
}
```
Tool: `NASA Data:get_notifications` (Server: NASA Data)
Description: Get DONKI notifications.
Args:
start_date: Start date in YYYY-MM-DD format. Defaults to 7 days before current date.
end_date: End date in YYYY-MM-DD format. Defaults to current date.
notification_type: Notification type. Options: all, FLR, SEP, CME, IPS, MPC, GST, RBE, report.
Input Schema:
```json
{
"properties": {
"start_date": {
"default": null,
"title": "Start Date",
"type": "string"
},
"end_date": {
"default": null,
"title": "End Date",
"type": "string"
},
"notification_type": {
"default": "all",
"title": "Notification Type",
"type": "string"
}
},
"title": "get_notificationsArguments",
"type": "object"
}
```
Tool: `NASA Data:get_earth_imagery` (Server: NASA Data)
Description: Get Earth imagery from Landsat 8 satellite.
Args:
lat: Latitude.
lon: Longitude.
date: Image date in YYYY-MM-DD format. If not specified, the most recent image is used.
dim: Width and height of the image in degrees (0.025 degrees is approximately 2.7 km).
cloud_score: Calculate the percentage of the image covered by clouds (currently not available).
Input Schema:
```json
{
"properties": {
"lat": {
"title": "Lat",
"type": "number"
},
"lon": {
"title": "Lon",
"type": "number"
},
"date": {
"default": null,
"title": "Date",
"type": "string"
},
"dim": {
"default": 0.025,
"title": "Dim",
"type": "number"
},
"cloud_score": {
"default": false,
"title": "Cloud Score",
"type": "boolean"
}
},
"required": [
"lat",
"lon"
],
"title": "get_earth_imageryArguments",
"type": "object"
}
```
Tool: `NASA Data:get_earth_assets` (Server: NASA Data)
Description: Get information about available imagery assets for a specific location and date.
Args:
lat: Latitude.
lon: Longitude.
date: Date in YYYY-MM-DD format.
dim: Width and height of the image in degrees (0.025 degrees is approximately 2.7 km).
Input Schema:
```json
{
"properties": {
"lat": {
"title": "Lat",
"type": "number"
},
"lon": {
"title": "Lon",
"type": "number"
},
"date": {
"title": "Date",
"type": "string"
},
"dim": {
"default": 0.025,
"title": "Dim",
"type": "number"
}
},
"required": [
"lat",
"lon",
"date"
],
"title": "get_earth_assetsArguments",
"type": "object"
}
```
Tool: `NASA Data:get_epic_imagery` (Server: NASA Data)
Description: Get images from the EPIC (Earth Polychromatic Imaging Camera).
Args:
collection: Collection type. Options: natural, enhanced.
Input Schema:
```json
{
"properties": {
"collection": {
"default": "natural",
"title": "Collection",
"type": "string"
}
},
"title": "get_epic_imageryArguments",
"type": "object"
}
```
Tool: `NASA Data:get_epic_imagery_by_date` (Server: NASA Data)
Description: Get images from the EPIC (Earth Polychromatic Imaging Camera) for a specific date.
Args:
date: Date in YYYY-MM-DD format.
collection: Collection type. Options: natural, enhanced.
Input Schema:
```json
{
"properties": {
"date": {
"title": "Date",
"type": "string"
},
"collection": {
"default": "natural",
"title": "Collection",
"type": "string"
}
},
"required": [
"date"
],
"title": "get_epic_imagery_by_dateArguments",
"type": "object"
}
```
Tool: `NASA Data:get_epic_dates` (Server: NASA Data)
Description: Get available dates for EPIC images.
Args:
collection: Collection type. Options: natural, enhanced.
Input Schema:
```json
{
"properties": {
"collection": {
"default": "natural",
"title": "Collection",
"type": "string"
}
},
"title": "get_epic_datesArguments",
"type": "object"
}
```
Tool: `NASA Data:get_exoplanet_data` (Server: NASA Data)
Description: Get data from NASA's Exoplanet Archive.
Args:
query: Specific query to filter results using Exoplanet Archive syntax. Example: "pl_orbper > 300 and pl_rade < 2"
table: Table to query. Common options: exoplanets (confirmed planets), cumulative (Kepler Objects of Interest), koi (subset of cumulative), tce (Threshold Crossing Events).
format: Output format. Options: json, csv, xml, ipac. Default: json.
Input Schema:
```json
{
"properties": {
"query": {
"default": null,
"title": "Query",
"type": "string"
},
"table": {
"default": "exoplanets",
"title": "Table",
"type": "string"
},
"format": {
"default": "json",
"title": "Format",
"type": "string"
}
},
"title": "get_exoplanet_dataArguments",
"type": "object"
}
```
Tool: `NASA Data:get_mars_rover_photos` (Server: NASA Data)
Description: Get photos from a Mars rover (Curiosity, Opportunity, Spirit).
Specify either sol (Martian day) or earth_date (YYYY-MM-DD), but not both.
Args:
rover_name: Name of the rover (curiosity, opportunity, spirit).
sol: Martian sol (day number, starting from landing). Use if not using earth_date.
earth_date: Earth date in YYYY-MM-DD format. Use if not using sol.
camera: Filter by camera abbreviation (e.g., FHAZ, RHAZ, MAST, NAVCAM, PANCAM). See documentation for full list per rover.
page: Page number for results (25 photos per page).
Input Schema:
```json
{
"properties": {
"rover_name": {
"title": "Rover Name",
"type": "string"
},
"sol": {
"default": null,
"title": "Sol",
"type": "integer"
},
"earth_date": {
"default": null,
"title": "Earth Date",
"type": "string"
},
"camera": {
"default": null,
"title": "Camera",
"type": "string"
},
"page": {
"default": 1,
"title": "Page",
"type": "integer"
}
},
"required": [
"rover_name"
],
"title": "get_mars_rover_photosArguments",
"type": "object"
}
```
Tool: `NASA Data:get_mars_rover_manifest` (Server: NASA Data)
Description: Get the mission manifest for a Mars rover (Curiosity, Opportunity, Spirit).
Provides mission details like landing/launch dates, status, max sol/date, total photos, and photo counts per sol.
Args:
rover_name: Name of the rover (curiosity, opportunity, spirit).
Input Schema:
```json
{
"properties": {
"rover_name": {
"title": "Rover Name",
"type": "string"
}
},
"required": [
"rover_name"
],
"title": "get_mars_rover_manifestArguments",
"type": "object"
}
```
Tool: `National Parks:findParks` (Server: National Parks)
Description: Search for national parks based on state, name, activities, or other criteria
Input Schema:
```json
{
"type": "object",
"properties": {
"stateCode": {
"type": "string",
"description": "Filter parks by state code (e.g., \"CA\" for California, \"NY\" for New York). Multiple states can be comma-separated (e.g., \"CA,OR,WA\")"
},
"q": {
"type": "string",
"description": "Search term to filter parks by name or description"
},
"limit": {
"type": "number",
"description": "Maximum number of parks to return (default: 10, max: 50)"
},
"start": {
"type": "number",
"description": "Start position for results (useful for pagination)"
},
"activities": {
"type": "string",
"description": "Filter by available activities (e.g., \"hiking,camping\")"
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `National Parks:getParkDetails` (Server: National Parks)
Description: Get detailed information about a specific national park
Input Schema:
```json
{
"type": "object",
"properties": {
"parkCode": {
"type": "string",
"description": "The park code of the national park (e.g., \"yose\" for Yosemite, \"grca\" for Grand Canyon)"
}
},
"required": [
"parkCode"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `National Parks:getAlerts` (Server: National Parks)
Description: Get current alerts for national parks including closures, hazards, and important information
Input Schema:
```json
{
"type": "object",
"properties": {
"parkCode": {
"type": "string",
"description": "Filter alerts by park code (e.g., \"yose\" for Yosemite). Multiple parks can be comma-separated (e.g., \"yose,grca\")."
},
"limit": {
"type": "number",
"description": "Maximum number of alerts to return (default: 10, max: 50)"
},
"start": {
"type": "number",
"description": "Start position for results (useful for pagination)"
},
"q": {
"type": "string",
"description": "Search term to filter alerts by title or description"
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `National Parks:getVisitorCenters` (Server: National Parks)
Description: Get information about visitor centers and their operating hours
Input Schema:
```json
{
"type": "object",
"properties": {
"parkCode": {
"type": "string",
"description": "Filter visitor centers by park code (e.g., \"yose\" for Yosemite). Multiple parks can be comma-separated (e.g., \"yose,grca\")."
},
"limit": {
"type": "number",
"description": "Maximum number of visitor centers to return (default: 10, max: 50)"
},
"start": {
"type": "number",
"description": "Start position for results (useful for pagination)"
},
"q": {
"type": "string",
"description": "Search term to filter visitor centers by name or description"
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `National Parks:getCampgrounds` (Server: National Parks)
Description: Get information about available campgrounds and their amenities
Input Schema:
```json
{
"type": "object",
"properties": {
"parkCode": {
"type": "string",
"description": "Filter campgrounds by park code (e.g., \"yose\" for Yosemite). Multiple parks can be comma-separated (e.g., \"yose,grca\")."
},
"limit": {
"type": "number",
"description": "Maximum number of campgrounds to return (default: 10, max: 50)"
},
"start": {
"type": "number",
"description": "Start position for results (useful for pagination)"
},
"q": {
"type": "string",
"description": "Search term to filter campgrounds by name or description"
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `National Parks:getEvents` (Server: National Parks)
Description: Find upcoming events at parks
Input Schema:
```json
{
"type": "object",
"properties": {
"parkCode": {
"type": "string",
"description": "Filter events by park code (e.g., \"yose\" for Yosemite). Multiple parks can be comma-separated (e.g., \"yose,grca\")."
},
"limit": {
"type": "number",
"description": "Maximum number of events to return (default: 10, max: 50)"
},
"start": {
"type": "number",
"description": "Start position for results (useful for pagination)"
},
"dateStart": {
"type": "string",
"description": "Start date for filtering events (format: YYYY-MM-DD)"
},
"dateEnd": {
"type": "string",
"description": "End date for filtering events (format: YYYY-MM-DD)"
},
"q": {
"type": "string",
"description": "Search term to filter events by title or description"
}
},
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}
```
Tool: `NixOS:nixos_search` (Server: NixOS)
Description: Search NixOS packages, options, or programs.
Args:
query: Search term to look for
search_type: Type of search - "packages", "options", "programs", or "flakes"
limit: Maximum number of results to return (1-100)
channel: NixOS channel to search in (e.g., "unstable", "stable", "25.05")
Returns:
Plain text results with bullet points or error message
Input Schema:
```json
{
"properties": {
"query": {
"title": "Query",
"type": "string"
},
"search_type": {
"default": "packages",
"title": "Search Type",
"type": "string"
},
"limit": {
"default": 20,
"title": "Limit",
"type": "integer"
},
"channel": {
"default": "unstable",
"title": "Channel",
"type": "string"
}
},
"required": [
"query"
],
"title": "nixos_searchArguments",
"type": "object"
}
```
Tool: `NixOS:nixos_info` (Server: NixOS)
Description: Get detailed info about a NixOS package or option.
Args:
name: Name of the package or option to look up
type: Type of lookup - "package" or "option"
channel: NixOS channel to search in (e.g., "unstable", "stable", "25.05")
Returns:
Plain text details about the package/option or error message
Input Schema:
```json
{
"properties": {
"name": {
"title": "Name",
"type": "string"
},
"type": {
"default": "package",
"title": "Type",
"type": "string"
},
"channel": {
"default": "unstable",
"title": "Channel",
"type": "string"
}
},
"required": [
"name"
],
"title": "nixos_infoArguments",
"type": "object"
}
```
Tool: `NixOS:nixos_channels` (Server: NixOS)
Description: List available NixOS channels with their status.
Returns:
Plain text list showing channel names, versions, and availability
Input Schema:
```json
{
"properties": {},
"title": "nixos_channelsArguments",
"type": "object"
}
```
Tool: `NixOS:nixos_stats` (Server: NixOS)
Description: Get NixOS statistics for a channel.
Args:
channel: NixOS channel to get stats for (e.g., "unstable", "stable", "25.05")
Returns:
Plain text statistics including package/option counts
Input Schema:
```json
{
"properties": {
"channel": {
"default": "unstable",
"title": "Channel",
"type": "string"
}
},
"title": "nixos_statsArguments",
"type": "object"
}
```
Tool: `NixOS:home_manager_search` (Server: NixOS)
Description: Search Home Manager configuration options.
Searches through available Home Manager options by name and description.
Args:
query: The search query string to match against option names and descriptions
limit: Maximum number of results to return (default: 20, max: 100)
Returns:
Plain text list of matching options with name, type, and description
Input Schema:
```json
{
"properties": {
"query": {
"title": "Query",
"type": "string"
},
"limit": {
"default": 20,
"title": "Limit",
"type": "integer"
}
},
"required": [
"query"
],
"title": "home_manager_searchArguments",
"type": "object"
}
```
Tool: `NixOS:home_manager_info` (Server: NixOS)
Description: Get detailed information about a specific Home Manager option.
Requires an exact option name match. If not found, suggests similar options.
Args:
name: The exact option name (e.g., 'programs.git.enable')
Returns:
Plain text with option details (name, type, description) or error with suggestions
Input Schema:
```json
{
"properties": {
"name": {
"title": "Name",
"type": "string"
}
},
"required": [
"name"
],
"title": "home_manager_infoArguments",
"type": "object"
}
```
Tool: `NixOS:home_manager_stats` (Server: NixOS)
Description: Get statistics about Home Manager options.
Retrieves overall statistics including total options, categories, and top categories.
Returns:
Plain text summary with total options, category count, and top 5 categories
Input Schema:
```json
{
"properties": {},
"title": "home_manager_statsArguments",
"type": "object"
}
```
Tool: `NixOS:home_manager_list_options` (Server: NixOS)
Description: List all Home Manager option categories.
Enumerates all top-level categories with their option counts.
Returns:
Plain text list of categories sorted alphabetically with option counts
Input Schema:
```json
{
"properties": {},
"title": "home_manager_list_optionsArguments",
"type": "object"
}
```
Tool: `NixOS:home_manager_options_by_prefix` (Server: NixOS)
Description: Get Home Manager options matching a specific prefix.
Useful for browsing options under a category or finding exact option names.
Args:
option_prefix: The prefix to match (e.g., 'programs.git' or 'services')
Returns:
Plain text list of options with the given prefix, including descriptions
Input Schema:
```json
{
"properties": {
"option_prefix": {
"title": "Option Prefix",
"type": "string"
}
},
"required": [
"option_prefix"
],
"title": "home_manager_options_by_prefixArguments",
"type": "object"
}
```
Tool: `NixOS:darwin_search` (Server: NixOS)
Description: Search nix-darwin (macOS) configuration options.
Searches through available nix-darwin options by name and description.
Args:
query: The search query string to match against option names and descriptions
limit: Maximum number of results to return (default: 20, max: 100)
Returns:
Plain text list of matching options with name, type, and description
Input Schema:
```json
{
"properties": {
"query": {
"title": "Query",
"type": "string"
},
"limit": {
"default": 20,
"title": "Limit",
"type": "integer"
}
},
"required": [
"query"
],
"title": "darwin_searchArguments",
"type": "object"
}
```
Tool: `NixOS:darwin_info` (Server: NixOS)
Description: Get detailed information about a specific nix-darwin option.
Requires an exact option name match. If not found, suggests similar options.
Args:
name: The exact option name (e.g., 'system.defaults.dock.autohide')
Returns:
Plain text with option details (name, type, description) or error with suggestions
Input Schema:
```json
{
"properties": {
"name": {
"title": "Name",
"type": "string"
}
},
"required": [
"name"
],
"title": "darwin_infoArguments",
"type": "object"
}
```
Tool: `NixOS:darwin_stats` (Server: NixOS)
Description: Get statistics about nix-darwin options.
Retrieves overall statistics including total options, categories, and top categories.
Returns:
Plain text summary with total options, category count, and top 5 categories
Input Schema:
```json
{
"properties": {},
"title": "darwin_statsArguments",
"type": "object"
}
```
Tool: `NixOS:darwin_list_options` (Server: NixOS)
Description: List all nix-darwin option categories.
Enumerates all top-level categories with their option counts.
Returns:
Plain text list of categories sorted alphabetically with option counts
Input Schema:
```json
{
"properties": {},
"title": "darwin_list_optionsArguments",
"type": "object"
}
```
Tool: `NixOS:darwin_options_by_prefix` (Server: NixOS)
Description: Get nix-darwin options matching a specific prefix.
Useful for browsing options under a category or finding exact option names.
Args:
option_prefix: The prefix to match (e.g., 'system.defaults' or 'services')
Returns:
Plain text list of options with the given prefix, including descriptions
Input Schema:
```json
{
"properties": {
"option_prefix": {
"title": "Option Prefix",
"type": "string"
}
},
"required": [
"option_prefix"
],
"title": "darwin_options_by_prefixArguments",
"type": "object"
}
```
Tool: `NixOS:nixos_flakes_stats` (Server: NixOS)
Description: Get statistics about available NixOS flakes.
Retrieves statistics from the flake search index including total packages,
unique repositories, flake types, and top contributors.
Returns:
Plain text summary with flake statistics and top contributors
Input Schema:
```json
{
"properties": {},
"title": "nixos_flakes_statsArguments",
"type": "object"
}
```
Tool: `NixOS:nixos_flakes_search` (Server: NixOS)
Description: Search NixOS flakes by name, description, owner, or repository.
Searches the flake index for community-contributed packages and configurations.
Flakes are indexed separately from official packages.
Args:
query: The search query (flake name, description, owner, or repository)
limit: Maximum number of results to return (default: 20, max: 100)
channel: Ignored - flakes use a separate indexing system
Returns:
Plain text list of unique flakes with their packages and metadata
Input Schema:
```json
{
"properties": {
"query": {
"title": "Query",
"type": "string"
},
"limit": {
"default": 20,
"title": "Limit",
"type": "integer"
},
"channel": {
"default": "unstable",
"title": "Channel",
"type": "string"
}
},
"required": [
"query"
],
"title": "nixos_flakes_searchArguments",
"type": "object"
}
```
Tool: `NixOS:nixhub_package_versions` (Server: NixOS)
Description: Get version history and nixpkgs commit hashes for a specific package from NixHub.io.
Use this tool when users need specific package versions or commit hashes for reproducible builds.
Args:
package_name: Name of the package to query (e.g., "firefox", "python")
limit: Maximum number of versions to return (default: 10, max: 50)
Returns:
Plain text with package info and version history including commit hashes
Input Schema:
```json
{
"properties": {
"package_name": {
"title": "Package Name",
"type": "string"
},
"limit": {
"default": 10,
"title": "Limit",
"type": "integer"
}
},
"required": [
"package_name"
],
"title": "nixhub_package_versionsArguments",
"type": "object"
}
```
Tool: `NixOS:nixhub_find_version` (Server: NixOS)
Description: Find a specific version of a package in NixHub with smart search.
Automatically searches with increasing limits to find the requested version.
Args:
package_name: Name of the package to query (e.g., "ruby", "python")
version: Specific version to find (e.g., "2.6.7", "3.5.9")
Returns:
Plain text with version info and commit hash if found, or helpful message if not
Input Schema:
```json
{
"properties": {
"package_name": {
"title": "Package Name",
"type": "string"
},
"version": {
"title": "Version",
"type": "string"
}
},
"required": [
"package_name",
"version"
],
"title": "nixhub_find_versionArguments",
"type": "object"
}
```
Tool: `Weather Data:get_current_weather_tool` (Server: Weather Data)
Description:
Get current weather information for a specific city.
Args:
city: Name of the city to get weather for
Returns:
Current weather data including temperature, conditions, humidity, wind, etc.
Input Schema:
```json
{
"properties": {
"city": {
"title": "City",
"type": "string"
}
},
"required": [
"city"
],
"title": "get_current_weather_toolArguments",
"type": "object"
}
```
Tool: `Weather Data:get_weather_forecast_tool` (Server: Weather Data)
Description:
Get weather forecast for a specific city.
Args:
city: Name of the city to get forecast for
days: Number of days to forecast (1-10, default: 3)
Returns:
Weather forecast data for the specified number of days
Input Schema:
```json
{
"properties": {
"city": {
"title": "City",
"type": "string"
},
"days": {
"default": 3,
"title": "Days",
"type": "integer"
}
},
"required": [
"city"
],
"title": "get_weather_forecast_toolArguments",
"type": "object"
}
```
Tool: `Weather Data:search_locations_tool` (Server: Weather Data)
Description:
Search for locations by name.
Args:
query: Location name or partial name to search for
Returns:
List of matching locations with their details
Input Schema:
```json
{
"properties": {
"query": {
"title": "Query",
"type": "string"
}
},
"required": [
"query"
],
"title": "search_locations_toolArguments",
"type": "object"
}
```
Tool: `Weather Data:get_live_temp` (Server: Weather Data)
Description:
Legacy tool: Get current temperature for a city (for backward compatibility).
Use get_current_weather_tool for more detailed information.
Input Schema:
```json
{
"properties": {
"city": {
"title": "City",
"type": "string"
}
},
"required": [
"city"
],
"title": "get_live_tempArguments",
"type": "object"
}
```
This is the first round - no previous execution results.
DECISION AND PLANNING:
1. Assess if the original task is fully completed
2. If not complete, decide if another round would provide significant value
3. If continuing, plan PARALLEL tool executions for this round
PARALLEL EXECUTION PLANNING (if continuing):
- Plan ALL tool calls for this round to execute in PARALLEL
- ALL tools in this round will run simultaneously without dependencies
- EARLY EXECUTION PRINCIPLE: Plan all necessary tool calls that don't require dependencies from other tools in this round
- AVOID REDUNDANT CALLS: Don't repeat successful tools unless specifically needed
- BUILD ON PREVIOUS RESULTS: Use information from previous rounds
- FOCUS ON INDEPENDENT TASKS: Plan tools that can work with currently available information
- You only have 20 rounds in total for solving the task.
Return your response in this exact JSON format:
{
"reasoning": "<Detailed explanation for your decision and parallel execution plan>",
"should_continue": <true/false>,
"planned_tools": [
{
"tool": "server:tool_name",
"parameters": { "param": "value" }
}
]
}
PARALLEL EXECUTION RULES:
- ALL tools in this round will run simultaneously
- NO dependencies between tools within the same round
- Each tool should work independently with available information
If not continuing, set "planned_tools" to an empty array [].
If continuing but no executions needed, also set "planned_tools" to an empty array [].
Return ONLY the JSON object.
<|im_end|>
<|im_start|>assistant
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment