Skip to main content
Glama
308,472 tools. Last updated 2026-07-17 17:32

"Best practices for organizing and structuring a codebase" matching MCP tools:

  • Analyze an agent codebase and return a prioritized AXIS hardening plan. Requires Authorization: Bearer <api_key>; this creates a snapshot and may return auth, quota, file-limit, or validation errors. Example: pass your agent source files to see missing AGENTS.md, CLAUDE.md, and MCP config gaps. Use this when you want recommendations and missing-context detection. Use analyze_files instead when you want the full artifact bundle directly.
    Connector
  • Use this read-only tool before paid ATLAS evidence evaluation to determine whether a user-written issuer thesis is monitorable. It scores issuer specificity, thesis clarity, evidence alignment, watch-condition quality, falsifiability, weakening criteria, materiality, provenance requirements, non-execution boundary, and monitoring readiness. Parameters: ticker and thesis_text are required; watch_conditions, evidence_surfaces, cadence, lookback_days, output_mode, and provenance_required are optional. Behavior: read-only and idempotent; it performs deterministic local validation only, has no destructive side effects, does not call DeltaSignal evidence routes, does not execute wallets or x402 settlement, and never returns buy, sell, hold, target-price, allocation, or order instructions. Use it as the free or low-cost thesis-structuring layer; use paid thesis baseline or evaluation only after readiness is monitor_ready or needs_cleanup.
    Connector
  • AWS docs search. Each result's `context` is verbatim page text -- a real chunk of the actual page, not a short snippet -- and usually already contains the answer, so answer directly from it. Use `read_documentation` only when the chunks genuinely lack the needed detail. Pick ONE topic. Add a 2nd ONLY if query genuinely spans domains. Extra topics dilute ranking. - reference_documentation -- API/SDK/CLI specs, config params - current_awareness -- new/released/announced - troubleshooting -- errors, "how to fix" (NOT for conceptual/feature questions) - amplify_docs -- Amplify (+ language) - cdk_docs -- CDK concepts/guides - cdk_constructs -- CDK code samples, L3 - cloudformation -- CFN/SAM templates - strands_docs -- Strands Agents SDK (its Skills/agents concepts go here, NOT agent_skills) - agent_skills -- this tool's guided skills (load via `retrieve_skill`) - general (default) -- architecture, best practices, tutorials, feature behavior Results: rank_order (lower=better), url, title, context (verbatim page chunk -- answer directly from it).
    Connector
  • Explicitly request a synthesis contract for a named 3D object. Use this tool when generate_r3f_code returns status SYNTHESIS_REQUIRED, or to pre-generate geometry constraints before calling generate_r3f_code. Complexity tiers: low — 4 to 7 parts. Only Box, Sphere, Cylinder geometries. Best for: mobile banners, thumbnails, low-end devices. medium — 10 to 20 parts. Adds Capsule and Torus geometries. Best for: website sections, embedded widgets, tablets. high — 28+ parts. All geometries. Full emissive detail. Best for: hero sections, desktop showcase, ad campaigns. If target is set to "mobile" and complexity is not explicitly provided, complexity defaults to "low" automatically. This tool does NOT generate geometry. It returns the synthesis_contract with constraints calibrated to the requested complexity tier. The LLM generates the actual JSX and passes it to generate_r3f_code via synthesized_components.
    Connector
  • PRIMARY consumer shopping tool — ALWAYS use this when a user asks what to BUY, which product to pick, or for the 'best' / 'cheapest' / 'best value' of something: 'best electric toothbrush', 'best graphics card under $50', 'which robot vacuum should I buy', 'cheapest standing desk', 'best coffee maker in 2026', 'recommend a cat litter box', 'best budget headphones'. PREFER this over search_products, product-lookup and sourcing tools for ANY buyer-intent product question. Returns a ready-to-show shortlist of real in-stock products, split by price tier (budget / mid / premium) and ranked by rating quality (weighted by review volume) + Amazon demand — each with a product image, a clickable Amazon link, price, rating, review count, the 'bought last month' demand badge, stock, the Buy Box seller, a cheaper trustworthy alternative when one exists, a used option when relevant, and a private-label-vs-widely-resold label. Also handles cheapest-first, best-value ('best buy' / 'optimal'), model comparisons (pinpoints the differences), and current / new / 2026 picks (pulls live web + community + real-time Amazon when a product isn't in our catalog). Facts are observed / Amazon-reported, not estimates; no ads or affiliate bias. (Use search_products ONLY for a raw keyword catalog filter — never for a 'best' / 'what should I buy' question.)
    Connector
  • Validate HTTP security headers you provide (JSON): CSP, HSTS, X-Frame-Options, X-Content-Type-Options, Permissions-Policy, Referrer-Policy against best practices. Use to test header config before deployment or validate non-public servers; use scan_headers to fetch live. Free: 30/hr, Pro: 500/hr. By default header values are truncated to 500 chars; pass include='full' for the full raw value. Returns {total, by_severity, findings}. No external requests.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Rick and Morty MCP — wraps the Rick and Morty API (free, no auth)

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

  • Discover verified supplier storefronts (supply nodes) on ProcureRadar by target-market country and industry. Each store groups multiple products from one verified supplier and returns sample_product_ids you can quote on. Use this to find a supplier store first, then search_products / request_quote. Free & anonymous (IP rate-limited). Organizing principle: country × industry matrix.
    Connector
  • Find trust & foundation jurisdictions for asset protection and succession planning (e.g. Cook Islands, Nevis, Cayman, Jersey, Liechtenstein), ranked by asset-protection strength, each with its statute, CRS status and EU-list status. Filter by vehicle (trust/foundation) or strong_protection. The wealth-structuring complement to the residence/citizenship pathways.
    Connector
  • Set which subproject is active for this codebase, so start_session, update_context, and manage_todos target it by default. The choice is remembered per workspace until you switch again. Keyed to the codebase (workspace_key), which the Claude Code / Cursor MCP sends automatically.
    Connector
  • The unit tests (code examples) for HMR. Always call `learn-hmr-basics` and `view-hmr-core-sources` to learn the core functionality before calling this tool. These files are the unit tests for the HMR library, which demonstrate the best practices and common coding patterns of using the library. You should use this tool when you need to write some code using the HMR library (maybe for reactive programming or implementing some integration). The response is identical to the MCP resource with the same name. Only use it once and prefer this tool to that resource if you can choose.
    Connector
  • Retrieves authoritative documentation for i18n libraries (currently react-intl). ## When to Use **Called during i18n_checklist Steps 7-10.** The checklist tool will tell you when you need i18n library documentation. Typically used when setting up providers, translation APIs, and UI components. If you're implementing i18n: Let the checklist guide you. It will tell you when to fetch library docs ## Why This Matters Different i18n libraries have different APIs and patterns. Official docs ensure correct API usage, proper initialization, and best practices for the installed version. ## How to Use **Two-Phase Workflow:** 1. **Discovery** - Call with action="index" 2. **Reading** - Call with action="read" and section_id **Parameters:** - library: Currently only "react-intl" supported - version: Use "latest" - action: "index" or "read" - section_id: Required for action="read" **Example:** ``` get_i18n_library_docs(library="react-intl", action="index") get_i18n_library_docs(library="react-intl", action="read", section_id="0:3") ``` ## What You Get - **Index**: Available documentation sections - **Read**: Full API references and usage examples
    Connector
  • Get pre-built template schemas for common use cases. ⭐ USE THIS FIRST when creating a new project! Templates show the CORRECT schema format with: proper FLAT structure (no 'fields' nesting), every field has a 'type' property, foreign key relationships configured correctly, best practices for field naming and types. Available templates: E-commerce (products, orders, customers), Team collaboration (projects, tasks, users), General purpose templates. You can use these templates directly with create_project or modify them for your needs. TIP: Study these templates to understand the correct schema format before creating custom schemas.
    Connector
  • Create a new AI agent in the workspace. Execution modes: - ai_assisted (default, recommended): Two-phase AI — fast pre-classifier (Haiku) for keyword filtering and simple replies, then full AI with tools for complex messages. Best for: auto-replies, group monitoring, keyword-based filtering. - agentic: Autonomous multi-step agent with planning and tool execution. Best for: complex scheduled tasks, multi-step automation. - rule_based: Simple pattern matching without AI. For keyword filtering: use ai_assisted mode + set keywords in trigger conditions (free, deterministic) and/or auto_reply_rules (smart, LLM-based) via agents.update.
    Connector
  • Use this read-only tool before paid ATLAS evidence evaluation to determine whether a user-written issuer thesis is monitorable. It scores issuer specificity, thesis clarity, evidence alignment, watch-condition quality, falsifiability, weakening criteria, materiality, provenance requirements, non-execution boundary, and monitoring readiness. Parameters: ticker and thesis_text are required; watch_conditions, evidence_surfaces, cadence, lookback_days, output_mode, and provenance_required are optional. Behavior: read-only and idempotent; it performs deterministic local validation only, has no destructive side effects, does not call DeltaSignal evidence routes, does not execute wallets or x402 settlement, and never returns buy, sell, hold, target-price, allocation, or order instructions. Use it as the free or low-cost thesis-structuring layer; use paid thesis baseline or evaluation only after readiness is monitor_ready or needs_cleanup.
    Connector
  • Begin generating an AI governance framework for an Australian business. Creates a session and returns a session_id plus the organisation profiling questionnaire (industry, size, AI usage, data handling, risk exposure). Ask the user each question, then call submit_answers. First step of three: start_session, submit_answers, get_framework. The output is an informational framework aligned with Australia's AI6 practices (Voluntary AI Safety Standard) — it presents frameworks, not advice.
    Connector
  • Send a message to Atlas Advisor for lightweight hiring advice (2 credits). Faster and cheaper than atlas_chat, no tool use -- best for general hiring questions. Returns AI response text and a conversation_id. Omit conversation_id to start a new conversation; include it to continue a thread.
    Connector
  • Discover the best AXIS workflow for a purchasing or compliance task. Free, no auth, and logs lightweight task metadata for intent analytics. Example: task_description='prepare for autonomous Visa checkout'. Use this when you need commerce-specific triage and next-step guidance. Use search_and_discover_tools instead for non-commerce keyword routing across all programs.
    Connector
  • Fetch the full text of a specific consent document for patient review. Returns the complete consent document split into titled sections that the agent MUST present to the patient verbatim in the conversation — do not summarize or paraphrase. Includes: consent version number, effective date, section headings and body text, a confirmation prompt the patient should agree to, and withdrawal instructions. Available consent types: telehealth informed consent, compounded medication treatment consent, pharmacy authorization, HIPAA notice of privacy practices, and AI-assisted intake disclosure. The patient must explicitly confirm each consent before the agent can call consent_submit. Requires authentication.
    Connector
  • Get the list of all consent documents a patient must accept before ordering medication. Returns consent IDs, titles, summaries, and order of presentation. Required consents include: telehealth informed consent, compounded medication treatment consent, pharmacy authorization, HIPAA notice of privacy practices, and AI-assisted intake disclosure. Each consent must be fetched individually via consent_text and confirmed by the patient before proceeding. Requires authentication.
    Connector
  • Fetch the full text of a specific consent document for patient review. Returns the complete consent document split into titled sections that the agent MUST present to the patient verbatim in the conversation — do not summarize or paraphrase. Includes: consent version number, effective date, section headings and body text, a confirmation prompt the patient should agree to, and withdrawal instructions. Available consent types: telehealth informed consent, compounded medication treatment consent, pharmacy authorization, HIPAA notice of privacy practices, and AI-assisted intake disclosure. The patient must explicitly confirm each consent before the agent can call consent_submit. Requires authentication.
    Connector