Skip to main content
Glama
206,803 tools. Last updated 2026-06-17 15:46

"General search for 'task'" matching MCP tools:

  • Search RealOpen's frequently asked questions by keyword and/or category. Use this when a user asks a specific question about RealOpen's process, security, timing, taxes, closing, proof of funds, or other product details — returns up to 20 matching entries. When no entries match, responds with the list of available categories so the caller can refine the query. Prefer this over guessing from general knowledge.
    Connector
  • Search CJEU (Court of Justice of the EU) and General Court case law — judgments, orders, and Advocate General opinions. Distinct from eurlex_search_documents because case law uses CELEX sector 6 and practitioners search it differently: by case number, court, party name, or AG opinion type. Keyword search matches against English expression titles and CELEX strings — full-text body search is not available. Case numbers follow the pattern C-{num}/{year} for CJEU and T-{num}/{year} for General Court (e.g. C-131/12). Returns case identifier, court, date, human-readable document type, and title (where available). Use eurlex_get_document with the CELEX number to fetch the full judgment text.
    Connector
  • Create a Google Ads experiment in SETUP status. Step 1 of 5 — next call addExperimentArms with one control + one treatment arm. Type `SEARCH_CUSTOM` for general search experiments (compare ads/keywords/landing pages); `SEARCH_AUTOMATED_BIDDING_STRATEGY` to compare bidding strategies on the same campaign. The experiment doesn't serve traffic until scheduleExperiment is called. Returns experimentResourceName.
    Connector
  • Search the web for current information on any topic. Returns extracted page content, not just snippets. Best for factual lookups, specific questions, or when you need a list of sources. For open-ended questions that need synthesis across many sources, use the research tool instead. For news queries (current events, breaking news, politics, world events), set topic="news" to search news sources specifically. This returns recent articles with publication dates. Set include_answer=true to get an AI-synthesized answer alongside results (adds 5 credits). This is the sweet spot for most agent tasks, e.g. basic + include_answer = 8 credits, much cheaper than a full 25-credit research call. Returns: query, answer (if requested), results (array of {title, url, content, description, fetched, published_date}), search_depth, topic, elapsed_ms, credits_used, credits_remaining, altered_query. Args: query: The search query search_depth: "basic" (default) for extracted page content (3 credits), "snippets" for SERP snippets only without page fetching (1 credit) max_results: Number of results (default 10, max 20) include_answer: Generate an AI answer that synthesizes the search results (adds 5 credits) include_domains: Only include results from these domains (max 10) exclude_domains: Exclude results from these domains (max 10) topic: "general" for web search, "news" for news articles. use "news" for current events, breaking news, politics, or any time-sensitive query freshness: Filter by recency - "day", "week", "month", "year", or "YYYY-MM-DD:YYYY-MM-DD"
    Connector
  • # AWS Documentation Search Tool Use this tool to find relevant AWS documentation — always follow up with `read_documentation` to get complete answers. Prefer this over general knowledge for AWS services, features, configurations, troubleshooting, and best practices. ## When to Use This Tool **Always search when the query involves:** - Any AWS service or feature (Lambda, S3, EC2, RDS, etc.) - AWS architecture, patterns, or best practices - AWS CLI, SDK, or API usage - AWS CDK or CloudFormation - AWS Amplify development - AWS errors or troubleshooting - AWS pricing, limits, or quotas - Strands Agents development - "How do I..." questions about AWS - Recent AWS updates or announcements **Only skip this tool when:** - Query is about non-AWS technologies - Question is purely conceptual (e.g., "What is a database?") - General programming questions unrelated to AWS ## Skill Suggestions for Actionable Queries When your search query matches tasks that benefit from domain-specific expertise, this tool will suggest relevant **Agent Skills**. Skills package domain knowledge, workflows, best practices, decision frameworks, and reference materials that make you a specialist in a particular AWS domain. **How it works:** - Your search query is scored against the skills registry using semantic search over skill descriptions and metadata tags - If your query matches a skill's domain, relevant skills are returned alongside documentation results - Skills cover a wide range of domains: deployment, troubleshooting, security, optimization, architecture, and more - To load a suggested skill, use the `retrieve_skill` tool with the `skill_name` - Once loaded, follow the skill's workflows and retrieve any referenced files as needed **Example queries that may return skills:** - "deploy a web application to AWS" — may return a deployment skill with architecture guidance and step-by-step deployment instructions - "debug Lambda cold start issues" — may return a troubleshooting skill with diagnostic workflows - "secure S3 buckets" — may return a security skill with best practices and compliance checklists - "optimize API Gateway latency" — may return a performance skill with decision frameworks - "set up VPC peering" — may return a networking skill with step-by-step procedures ## Quick Topic Selection | Query Type | Use Topic | Example | |------------|-----------|-------| | API/SDK/CLI code | `reference_documentation` | "S3 PutObject boto3", "Lambda invoke API" | | New features, releases | `current_awareness` | "Lambda new features 2024", "what's new in ECS" | | Errors, debugging | `troubleshooting` | "AccessDenied S3", "Lambda timeout error" | | Amplify apps | `amplify_docs` | "Amplify Auth React", "Amplify Storage Flutter" | | CDK concepts, APIs, CLI | `cdk_docs` | "CDK stack props Python", "cdk deploy command" | | CDK code samples, patterns | `cdk_constructs` | "serverless API CDK", "Lambda function example TypeScript" | | CloudFormation templates | `cloudformation` | "DynamoDB CloudFormation", "StackSets template" | | Architecture, blogs, guides | `general` | "Lambda best practices", "S3 architecture patterns" | | Strands Agents | `strands_docs` | "Strands Agents Python structured output", "Strands Agents AWS CDK EC2 Deployment Example" | | Domain expertise, workflows, guided procedures | `agent_skills` | "deploy serverless app", "debug Lambda cold starts", "secure IAM policies" | ## Documentation Topics ### reference_documentation **For: API methods, SDK code, CLI commands, technical specifications** Use for: - SDK method signatures: "boto3 S3 upload_file parameters" - CLI commands: "aws ec2 describe-instances syntax" - API references: "Lambda InvokeFunction API" - Service configuration: "RDS parameter groups" Don't confuse with general—use this for specific technical implementation. ### current_awareness **For: New features, announcements, "what's new", release dates** Use for: - "New Lambda features" - "When was EventBridge Scheduler released" - "Latest S3 updates" - "Is feature X available yet" Keywords: new, recent, latest, announced, released, launch, available ### troubleshooting **For: Error messages, debugging, problems, "not working"** Use for: - Error codes: "InvalidParameterValue", "AccessDenied" - Problems: "Lambda function timing out" - Debug scenarios: "S3 bucket policy not working" - "How to fix..." queries Keywords: error, failed, issue, problem, not working, how to fix, how to resolve ### amplify_docs **For: Frontend/mobile apps with Amplify framework** Always include framework: React, Next.js, Angular, Vue, JavaScript, React Native, Flutter, Android, Swift Examples: - "Amplify authentication React" - "Amplify GraphQL API Next.js" - "Amplify Storage Flutter setup" ### cdk_docs **For: CDK concepts, API references, CLI commands, getting started** Use for CDK questions like: - "How to get started with CDK" - "CDK stack construct TypeScript" - "cdk deploy command options" - "CDK best practices Python" - "What are CDK constructs" Include language: Python, TypeScript, Java, C#, Go **Common mistake**: Using general knowledge instead of searching for CDK concepts and guides. Always search for CDK questions! ### cdk_constructs **For: CDK code examples, patterns, L3 constructs, sample implementations** Use for: - Working code: "Lambda function CDK Python example" - Patterns: "API Gateway Lambda CDK pattern" - Sample apps: "Serverless application CDK TypeScript" - L3 constructs: "ECS service construct" Include language: Python, TypeScript, Java, C#, Go ### cloudformation **For: CloudFormation templates, concepts, SAM patterns** Use for: - "CloudFormation StackSets" - "DynamoDB table template" - "SAM API Gateway Lambda" - "CloudFormation template examples" ### strands_docs **For: Strands Agents API reference, integrations, model providers, session managers, tools, examples, user-guide** Use for: - "Strands Agents Python SDK example" - "Strands Agents AWS integration" - "Strands Agents community contributions" - "Strands Agents usage examples" - "Strands Agents usage guide" ### general **For: Architecture, best practices, tutorials, blog posts, design patterns** Use for: - Architecture patterns: "Serverless architecture AWS" - Best practices: "S3 security best practices" - Design guidance: "Multi-region architecture" - Getting started: "Building data lakes on AWS" - Tutorials and blog posts **Common mistake**: Not using this for AWS conceptual and architectural questions. Always search for AWS best practices and patterns! **Don't use general knowledge for AWS topics—search instead!** ### agent_skills **For: Discovering agent skills — domain-specific expertise packages for AWS workflows** Use for: - Complex tasks that benefit from guided workflows: "deploy a serverless application" - Troubleshooting scenarios: "debug Lambda cold starts", "resolve ECS task failures" - Security and compliance: "secure S3 buckets", "review IAM policies for least privilege" - Architecture and optimization: "optimize API Gateway latency", "design multi-region architecture" - When you need domain expertise beyond what documentation provides Skills go beyond documentation — they provide workflows, decision frameworks, best practices, and may include embedded procedures for critical sub-tasks. **Important**: This topic is meant for discovery. Once you identify the skill you need, use `retrieve_skill` tool with the `skill_name` to load the full skill and its reference materials. **Note**: If combined with other topics, skills will be mixed into the documentation results. Use `agent_skills` alone for a clean skill-only listing. ## Search Best Practices **Be specific with service names:** Good examples: ``` "S3 bucket versioning configuration" "Lambda environment variables Python SDK" "DynamoDB GSI query patterns" ``` Bad examples: ``` "versioning" (too vague) "environment variables" (missing context) ``` **Include framework/language:** ``` "Amplify authentication React" "CDK Lambda function TypeScript" "boto3 S3 client Python" ``` **Use exact error messages:** ``` "AccessDenied error S3 GetObject" "InvalidParameterValue Lambda environment" ``` **Add temporal context for new features:** ``` "Lambda new features 2024" "recent S3 announcements" ``` **If the first search does not return results that directly answer the question, refine your query and search again with different terms, a more specific phrase, or a different topic. Try conceptual/architectural topics (general, blogs) if reference docs are too narrow.** **After searching, use `read_documentation` on the top-ranked URLs to verify and complete your answer.** ## Multiple Topic Selection You can search multiple topics simultaneously for comprehensive results: ``` # For a query about Lambda errors and new features: topics=["troubleshooting", "current_awareness"] # For CDK examples and API reference: topics=["cdk_constructs", "cdk_docs"] # For Amplify and general AWS architecture: topics=["amplify_docs", "general"] # For actionable tasks: topics=["agent_skills"] ``` ## Response Format Results include: - `rank_order`: Relevance score (lower = more relevant) - `url`: Direct documentation link — use with `read_documentation` to get the full page content - `title`: Page title - `context`: Partial excerpt only — not the complete documentation. After reviewing results, call `read_documentation` on the most relevant URLs before answering. Do not answer based on the context excerpt alone. ## Parameters ``` search_phrase: str # Required - your search query topics: List[str] # Optional - up to 3 topics. Defaults to ["general"] limit: int = 5 # Optional - max results per topic ``` --- **Remember: When in doubt about AWS, always search. This tool provides the most current, accurate AWS information. But search is only step 1 — always read the full documentation to give complete answers.**
    Connector
  • Run a pre-configured saved task from the user's CoreClaw console. All parameters are stored with the task — no input schema needed. WHEN TO USE: the user wants to execute a named saved task they already configured in CoreClaw — "跑一下我那个 amazon 日常任务"、"run my saved task X"、"execute task Y". User refers to the task by task_slug (different from scraper_slug). WHEN NOT TO USE: do NOT use for ad-hoc runs with custom parameters (use run_scraper). Do NOT use to re-run a past run (use rerun). RETURNS: JSON with 'run_slug' (use for get_run_status / get_run_results), 'status'. WORKFLOW: terminal call for starting work. Follow with get_run_status -> get_run_results.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • An MCP server for deep research or task groups

  • Give your AI agent a phone. Place outbound calls to US businesses to ask, book, or confirm.

  • General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)
    Connector
  • Create a new forum topic (bug report, feature request, or general discussion). Always call forum_search first to check for duplicates. Call forum_list_categories to get the correct categoryId.
    Connector
  • Check submissions for a task you published. Use this to see if a human has submitted evidence for your task. You can then use em_approve_submission to accept or reject. Args: params (CheckSubmissionInput): Validated input parameters containing: - task_id (str): UUID of the task - agent_id (str): Your agent ID (for authorization) - response_format (ResponseFormat): markdown or json Returns: str: Submission details or "No submissions yet".
    Connector
  • Full-text book search across Open Library works. Supports field filters (title, author, subject, publisher, ISBN, language) and returns work-level records with edition counts, cover IDs, and reading availability. Use query for general search or combine specific field filters. Results are work-level — drill into editions via openlibrary_get_editions.
    Connector
  • Full-text search within one post's comment thread. Scoped to a single ``post_id`` — there is no cross-post comment search here; use ``colony_search`` for general discovery. Returns hits newest-first with ``ts_headline`` snippets (``[[hl]]…[[/hl]]`` around matched terms) and ``path_to_root`` — the ancestor chain walking from immediate parent up to top-level — so the caller can show "in reply to" context. Tombstoned comments are excluded. Cursor pagination: pass the response's ``next_cursor`` back as ``cursor`` on the next call. ``has_more`` flips to false on the last page. Authentication is required (same bearer-token shape as the rest of the comment tools).
    Connector
  • General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)
    Connector
  • Submit completed work with evidence for an assigned task. After completing a task, use this to submit your evidence for review. The agent will verify your submission and release payment if approved. Requirements: - You must be assigned to this task - Task must be in 'accepted' or 'in_progress' status - Evidence must match the task's evidence_schema - All required evidence fields must be provided Args: params (SubmitWorkInput): Validated input parameters containing: - task_id (str): UUID of the task - executor_id (str): Your executor ID - evidence (dict): Evidence matching the task's requirements - notes (str): Optional notes about the submission Returns: str: Confirmation of submission or error message. Status Flow: accepted/in_progress -> submitted -> verifying -> completed Evidence Format Examples: Photo task: {"photo": "ipfs://Qm...", "gps": {"lat": 25.76, "lng": -80.19}} Document task: {"document": "https://storage.../doc.pdf", "timestamp": "2026-01-25T10:30:00Z"} Observation task: {"text_response": "Store is open, 5 people in line", "photo": "ipfs://..."}
    Connector
  • General-purpose web grounding via parallel.ai (Vercel AI Gateway). Returns synthesized text excerpts plus structured sources[] with direct URLs. Use for: topic landscapes, entity-deep teardowns, recency-sharp queries, named-vendor lookups, general fact retrieval. NOT for: Reddit/X/community discourse → use search_community. NOT for: numerical effect sizes or methodology-heavy fact-check → use search_research. The agent decomposes the brief into sub-questions BEFORE calling — one focused query per call. Optional after_date (ISO YYYY-MM-DD) for fast-decay topics. Optional max_results 1-20, default 10.
    Connector
  • Task-scoped context briefing. Returns a prioritised context payload shaped by your task description, ranked by risk-if-missed. Constraints and alerts rank above general knowledge. Use at the START of reasoning about a question to get the system's best assessment of what's relevant. Complements query_memory: this gives breadth, query_memory gives depth.
    Connector
  • Search MCP servers by server title/name, description, or by the tools they provide. Accepts natural language capability queries like 'send emails', 'search the web', 'create pull requests', or direct server names like 'GitHub' or 'Stripe'. Results are ranked by relevance: title match first, then tool name match, then description. Each result includes the server's tool list so you can confirm it does what you need. Set limit based on the type of request you received: - Prompting (general/exploratory — user is browsing or asking broadly): use 20-30 - Task assignment (user delegated a goal for you to execute autonomously): use 10-15 - Instruction/directive (specific command with a clear target server in mind): use 3-5
    Connector
  • Search Redpanda API reference documentation by keyword. Returns up to 20 matching endpoints, schemas, or topics with URL, title, and text excerpts. SCOPING (important for accurate results): - api="all" or omit: Search across ALL APIs at once - useful when unsure which API contains the endpoint - api="admin": Search only cluster management (brokers, partitions, configs, users, maintenance) - api="cloud-controlplane": Search only Cloud resource management (clusters, networks, namespaces) - api="cloud-dataplane": Search only Cloud data operations (topics, ACLs, connectors) - api="http-proxy": Search only HTTP Proxy (produce, consume, offsets over HTTP) - api="schema-registry": Search only Schema Registry (register, retrieve, compatibility) WHEN TO USE WHICH: - User asks "broker endpoints" → api="admin" (brokers are cluster management) - User asks "create topic API" → api="all" (topics exist in admin AND cloud-dataplane) - User asks "Cloud cluster API" → api="cloud-controlplane" - User asks about Redpanda APIs generally → api="all" or omit For general Redpanda questions (not API-specific), use ask_redpanda_question instead.
    Connector
  • Keyword-search AI entities using the task text as query input. Returns FNI-ranked catalog entries. Does not perform task-fit recommendation or compatibility analysis. Read-only, no side effects. May return a retryable transient 503 under cold-path or fallback budget limits; retry according to Retry-After. Use free2aitools_search for keyword-based discovery, or free2aitools_select_model to apply hardware/license metadata filters.
    Connector
  • Loads one supported self-assessment into the widget by slug. Use `gad7` for anxiety screening, `phq9` for depression screening, and `who5` for general well-being screening when the user wants to take one of those assessments.
    Connector
  • Search for solutions other agents already discovered. STOP and search before acting on any error — even mid-task. Do not chain fixes without searching each one. When: Any error, compile failure, stack trace, or unexpected output. Before config, integration, or setup tasks. When a fix attempt just failed — search before trying the next one. Unfamiliar library or framework combination. Do not skip because the fix seems obvious — obvious fixes are the most common and most likely to already be solved. How: Paste the exact error message, not your goal. Include framework or language name. Read failedApproaches first to skip dead ends. Feedback: Include previousSearchFeedback to rate a result from your last search — this refunds your search credit and costs nothing extra.
    Connector