Skip to main content
Glama
128,576 tools. Last updated 2026-05-06 03:05

"A tool or assistant to review and suggest changes for GitHub pull requests" matching MCP tools:

  • Apply targeted modifications to an existing scene_data object. WHEN TO CALL: - After validate_scene returns is_valid: false - When the user requests a style, material, animation, or position change to an already-generated scene - Do NOT call this to create a new scene — use generate_scene instead WHAT THIS TOOL CAN MODIFY: - background: color and style preset - material: for all objects or a named object - animation: add or replace animations on objects - position: move a named object or the primary object - lighting: intensity adjustments (darker / lighter) - design_tokens: kept in sync with all changes automatically WHAT THIS TOOL CANNOT DO: - Add new objects to the scene (use generate_scene for this) - Remove existing objects (out of scope in current version) - Change camera position or FOV - Modify individual mesh geometry INPUT: - scene_data: the full scene_data object from generate_scene or a previous edit_scene call - edit_prompt: a plain-language description of the desired change EDIT PROMPT EXAMPLES: - "make it darker" → dims ambient lighting, deepens background - "make the material glass" → applies glass_frost to all objects - "add spinning motion" → appends rotate animation, keeps existing - "move the robot up" → moves object named "robot" up by 1 unit - "change animation to float only" → replaces all animations with float - "make it neon" → applies neon material + neon_edge lighting OUTPUT: - scene_data: updated scene with all changes applied - edit_summary: { applied[], skipped[], warnings[] } PIPELINE POSITION: generate_scene → validate_scene → [edit_scene if invalid] → validate_scene (re-run) → synthesize_geometry → generate_r3f_code
    Connector
  • Build and deploy a governed AI Team solution in one step. ⚠️ HEAVIEST OPERATION (60-180s): validates solution+skills → deploys all connectors+skills to A-Team Core (regenerates MCP servers) → health-checks → optionally runs a warm test → auto-pushes to GitHub. AUTO-DETECTS GitHub repo: if you omit mcp_store and a repo exists, connector code is pulled from GitHub automatically. First deploy requires mcp_store. After that, write files via ateam_github_write, then just call build_and_run without mcp_store. For small changes to an already-deployed solution, prefer ateam_patch (faster, incremental). Requires authentication.
    Connector
  • Re-deploy skills WITHOUT changing any definitions. ⚠️ HEAVY OPERATION: regenerates MCP servers (Python code) for every skill, pushes each to A-Team Core, restarts connectors, and verifies tool discovery. Takes 30-120s depending on skill count. Use after connector restarts, Core hiccups, or stale state. For incremental changes, prefer ateam_patch (which updates + redeploys in one step).
    Connector
  • Search WhatDoTheyKnow's feed-based event index and return structured results. Call this to find FOI requests matching a query expression. Returns up to `limit` AtomEntry objects. Use the `link` field of each result as the next navigation step — extract the request slug and call the wdtk://requests/{slug} resource or get_request_feed_items for full detail. Example expressions: status:successful body:"Liverpool City Council" (variety:sent OR variety:response) status:successful
    Connector
  • Use when you have lost track of a task_id or want to review your past human task requests. Returns all tasks you have submitted, newest first: id, status, description, result, and timestamps.
    Connector
  • Find hiking, running, biking, backpacking or other trails for outdoor activities within a specified bounding box defined by southwest and northeast coordinates. Use this tool when the user: * Requests trails within specific geographic boundaries or coordinates. * Requests trails near a named geographic or political place, such as a continent, country, state, province, region, city, town, or neighborhood and you know the bounding box for that place. * Requests trails within a national, state or local park or other protected area and you know the bounding box for that park. If the bounding box for the named place is not known, use the "find trails near a location" tool instead to find trails around a center point. Users can specify filters related to appropriate activities, attractions, suitability, and more. Numeric range filters related to distance, elevation, and length are also available. These filter values MUST be specified in meters. In the response, length and distance values are returned both in meters and imperial units. These MUST be displayed to the user in the units most appropriate for the user's locale, e.g. feet or miles for US English users.
    Connector

Matching MCP Servers

  • A
    license
    -
    quality
    B
    maintenance
    Enables AI to perform peer review of its own code changes by displaying annotated diffs with inline comments in a VS Code/Cursor panel. The AI can analyze its modifications and provide explanations directly alongside the changed code, similar to human code review workflows.
    Last updated
    3
    MIT

Matching MCP Connectors

  • performance-review MCP — wraps StupidAPIs (requires X-API-Key)

  • GitHub MCP — wraps the GitHub public REST API (no auth required for public endpoints)

  • Scan a GitHub repository or skill URL for security vulnerabilities. This tool performs static analysis and AI-powered detection to identify: - Hardcoded credentials and API keys - Remote code execution patterns - Data exfiltration attempts - Privilege escalation risks - OWASP LLM Top 10 vulnerabilities Requires a valid X-API-Key header. Cached results (24h) do not consume credits. Args: skill_url: GitHub repository URL (e.g., https://github.com/owner/repo) or raw file URL to scan Returns: ScanResult with security score (0-100), recommendation, and detected issues. Score >= 80 is SAFE, 50-79 is CAUTION, < 50 is DANGEROUS. Example: scan_skill("https://github.com/anthropics/anthropic-sdk-python")
    Connector
  • Fetches the specific deposit address for the TronSave internal account. Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; the server forwards the API key cached in session to TronSave internal REST endpoints. Trigger this tool if the user asks for a deposit address or needs to top up their TronSave TRX balance. Constraints: 1) TRX only; 2) Minimum deposit amount is 10 TRX; 3) Read-only operation.
    Connector
  • Simplest way to contribute: just say if a tool worked or not. Automatically becomes a +1 or -1 review. Use AFTER you tried or recommended something and know the outcome.
    Connector
  • Find hiking, running, biking, backpacking or other trails for outdoor activities near a set of coordinates within an optional specified maximum radius (meters). Use this tool when the user: * Requests trails near a specific point of interest or landmark. * Requests trails near a named location within a specified radius or accessible within a specified time constraint. * Provides specific latitude and longitude coordinates. For most named places, use the "search within bounding box" tool if possible. Use this tool as a fallback when the bounding box of the named place is unknown. Users can specify filters related to appropriate activities, attractions, suitability, and more. Numeric range filters related to distance, elevation, and length are also available. These filter values MUST be specified in meters. In the response, length and distance values are returned both in meters and imperial units. These MUST be displayed to the user in the units most appropriate for the user's locale, e.g. feet or miles for US English users.
    Connector
  • List incoming RAI requests — inbox of pull requests from buyers, galleries, insurers, advisors, auction houses asking the artist for a verified record. TRIGGER: "show my requests," "what RAI requests do I have," "who's asking for authentication," "open my inbox," "anything waiting on me." Returns all statuses (pending, accepted, fulfilled, declined, expired). Pending items need artist action — surface them first.
    Connector
  • Fetches the specific deposit address for the TronSave internal account. Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; the server forwards the API key cached in session to TronSave internal REST endpoints. Trigger this tool if the user asks for a deposit address or needs to top up their TronSave TRX balance. Constraints: 1) TRX only; 2) Minimum deposit amount is 10 TRX; 3) Read-only operation.
    Connector
  • Upload connector code to Core and restart — WITHOUT redeploying skills. Use this to update connector source code (server.js, UI assets, plugins) quickly. Set github=true to pull files from the solution's GitHub repo, or pass files directly. Much faster than ateam_build_and_run for connector-only changes.
    Connector
  • Get recent shipping regulatory updates and compliance requirements for a specific country — customs regulations, documentation requirements, trade restrictions, and policy changes. Use this to stay current on regulatory changes that may affect shipments to/from a country. PAID: $0.01/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: Array of { title, description, effective_date, impact_level, category, country }.
    Connector
  • Check the current status of a previously submitted intake questionnaire. Returns whether the intake is under review, approved, or denied by a licensed healthcare provider. Use this to poll for provider review completion before proceeding to order placement. Requires authentication.
    Connector
  • [~] PRIORITY TRIGGER: Use this tool when user mentions 'PR', 'Pull Request', 'list PRs', 'show PRs', 'active PRs', 'mes PR', 'liste des PR', 'pull requests ouverts', 'what PRs are open', 'PRs by [author]', 'PRs targeting [branch]'. NEVER call search_d365_code for PR listing requests. List Pull Requests in an Azure DevOps Git repository. If `repositoryId` is unknown, omit it and all repositories will be listed first. Filters: status (Active/Completed/Abandoned/All), author display name, target branch. Returns: PR ID, title, author, source->target branch, review status, linked work items, creation date. Use `ado_analyze_pr_impact` with a PR ID to get full D365 code impact analysis. Requires DEVOPS_ORG_URL + DEVOPS_PAT (Code: Read scope).
    Connector
  • Provides step-by-step instructions for an AI assistant to set up a new JxBrowser project. This tool is meant for fully automated project creation and should be called when the user asks to create, start, scaffold, bootstrap, init, template, or generate a JxBrowser project, app, or sample. CRITICAL RULES: 1. NEVER call this tool before knowing the user’s preferences. If the user hasn’t specified them, ASK first: - UI Toolkit: Swing, JavaFX, SWT, or Compose Desktop - Build Tool: Gradle or Maven 2. Immediately after calling this tool, you MUST execute all setup commands returned by this tool using the Bash tool to actually create the project.
    Connector
  • Cast your expert +1 or -1 review on any entity. Use AFTER evaluating a tool you searched for or tried. Expert reviews are 70% of ranking. One review per agent per entity (overwrites previous). Requires agent_key. For no-auth alternative, use nanmesh.trust.favor instead.
    Connector
  • Get the deployment and version history (git commits) for a project. Shows all schema changes with commit SHA, timestamp, and message. USE CASES: Review what changed between deployments, find the last working version before issues started, get commit SHA for rollback_project.
    Connector