Skip to main content
Glama
605,932 tools. Updated 2026-09-24 06:19

"ANA" matching MCP tools:

  • Create a follow-up tied to a person — a to-do for the relationship (e.g. 'send the deck', 'intro to Ana'). In Team context, pass team_id and assigned_to to create it for any teammate against a Team-visible relationship. RECOMMENDED: include both assigned_to and remind_at whenever ownership and timing are known; neither is required. @mention a name in `content` to link someone in the relationship owner's network. Read open ones via get_person (relationship.actions); close them with complete_action or edit them with update_action.
    ConnectorNo auth
  • Analyze the structural shape of the AI-generated answer actually cited for a keyword: does it lead with a list, how long is the opening passage, how many sources does it cite and from which domains. Use this to understand what a winning AI-search answer looks like for a topic, e.g. before writing content meant to get cited. Read-only: no side effects, safe to retry. Costs 1 quota unit per sample (1 by default; free tier is 30 units/month shared across every metered tool, so up to 30 single-sample calls to this tool alone if nothing else is used that period). Returns: {"keyword", "engine", "model" (the answering model's version, as the provider reports it), "checked_at" (when the answer was fetched, UTC), "leads_with_list" (bool), "opening_word_count" (int), "opening_has_number" (bool), "outline" (list of up to 12 section heads, in order: the answer's headings, or its top-level list items when it has fewer than two headings; heads only, never the text under them), "has_table" (bool), "num_sources_cited" (int), "source_domains" (list of up to 10 domain strings), "source_mix" ({"community_pct" (share of those sources that are community sites such as Reddit, YouTube, X, Quora), "community_domains", "other_domains"}), "country", "language"}. With samples above 1 the shape fields describe the first answer, plus "samples_ok" (answers that came back) and "source_frequency" (list of {"domain", "runs"}: how many of the answers cited each domain, most often first). Answers change from run to run, so a domain cited in every sample is a far stronger signal than one sample. Use analyze_citation_structure_batch instead if you need this for more than one keyword - one call per topic here adds up fast for a cluster. Use analyze_citation_gap instead if you have your own page for this keyword and want the gap to the winner, not just the winner's shape. Args: keyword: the topic/query to analyze, e.g. "how to reduce churn". country: market to read the answer in, e.g. "Italy". Defaults to "United States". For perplexity a 2-letter code also works. language: language code, e.g. "it". Defaults to "en". Write the keyword in that language too. engine: "chat_gpt" (default), "gemini" or "perplexity". chat_gpt and gemini are the answers a person sees in those apps; perplexity is Perplexity's sonar API with web search. samples: how many independent answers to read, 1 to 5. Default 1.
    ConnectorAPI key
  • Analyze the structural shape of the winning AI answer across several related keywords/topics in one call: does each lead with a list, how long is the opening, how many sources it cites. Use this for content planning across a topic cluster, e.g. before writing several related pieces meant to get cited, instead of calling analyze_citation_structure once per topic. Read-only: no side effects, safe to retry. Costs 1 quota unit per keyword in the batch (free tier is 30 units/month shared across all the metered tools, so up to 30 keywords total that period if nothing else is used). A per-keyword provider error doesn't fail the whole batch - that keyword's entry just carries an "error" field instead. Returns: {"results" (list, one {"keyword", ...same shape as analyze_citation_structure, or "error"} per keyword, in the order given), "summary": {"topics_analyzed", "topics_requested", "list_led_count", "avg_sources_cited", "avg_community_pct" (average source_mix.community_pct across the analyzed topics)}}. Args: keywords: topics/queries to analyze, e.g. ["how to reduce churn", "churn rate benchmarks", "reduce customer churn saas"]. Max 10. country: market to read the answers in, e.g. "Italy". Defaults to "United States". language: language code, e.g. "it". Defaults to "en". engine: "chat_gpt" (default), "gemini" or "perplexity", as in analyze_citation_structure. One answer per topic.
    ConnectorAPI key
  • Compare your own page's structure against the AI-generated answer actually cited for this keyword, and return a fix brief: ordered rewrite instructions for your page, not just a description of the winner. Use this to answer 'what should I change on this page to get cited' rather than only 'what does a winning answer look like'. Carry out the fix_brief on the user's page in their own words; it never contains the cited answer's text. Read-only: no side effects, safe to retry. Costs 1 quota unit/call (free tier is 30 units/month shared across every metered tool, so up to 30 calls to this tool alone if nothing else is used that period). Returns: {"keyword", "your_url", "winning" (structure of the AI-cited answer, same shape as analyze_citation_structure), "yours" (same structure computed for your_url, including its own "outline" and "has_table", with "num_links_out"/"linked_domains" standing in for source count), "gaps" (list of plain-English differences worth acting on), "possibly_missing" (heads from the winning outline whose key words mostly do not appear on your page; word matching, so check each before adding it), "fix_brief" (list of instructions, most important first: opening, number, list, sections, missing points, table, sources, then a reminder to write in your own words - or a "no structural change indicated" line when every check already matches - and always last, one off-site step drawn from the winning answer's source_mix: which community sites (Reddit, YouTube, X...) it cites, or which other sites to get mentioned on. Page shape gets a page into the running; being cited is decided mostly by what other sites say about the brand)}, or {"error"} if either side couldn't be fetched/parsed. Use analyze_citation_structure instead if you just want the winning answer's shape, not a comparison against your own page. Use check_prompt_coverage first if you have several keywords and do not yet know which ones you are missing from - this tool is for one keyword you already know needs work. Args: keyword: the topic/query to check, e.g. "best project management tool". your_url: full URL of your own page to compare, e.g. "https://example.com/best-project-management-tools". country: market to read the cited answer in, e.g. "Italy". Defaults to "United States". language: language code, e.g. "it". Defaults to "en". engine: "chat_gpt" (default), "gemini" or "perplexity": whose answer to compare your page against.
    ConnectorAPI key
  • Calculation, not advice. Verify with a professional before acting. Compute every standard PMI-removal pathway: - HPA automatic at 78% LTV - HPA borrower-requested at 80% LTV - optional re-appraisal at a simplified 75% of current market value; the actual Fannie Mae ceiling is seasoning- and property-type-dependent, 75% for a one-unit home seasoned two to five years, 80% for five-plus, and 70% for investment and two- to four-unit properties Also returns current monthly PMI cost, total PMI dollars between now and automatic removal, and the effective annual return of paying the gap-to-80% (of the original value) as a lump sum today. Supplying original_loan_term_months and loan_age_months also applies the 12 U.S.C. 4902(c) statutory final-termination midpoint, which bounds automatic removal at the earlier of the 78% schedule and that midpoint where HPA applies and the borrower is current. Pairs with `calculate_refi_breakeven` for a refinance's rate-and-term break-even, and with `compare_mortgage_terms` when choosing between purchase mortgages. Scope: conventional mortgages only; FHA loans use MIP (Mortgage Insurance Premium) with different rules. This tool does not model MIP.
    ConnectorNo auth
  • Get a loyalty programme's PARTNER airline award chart (the points to book partner-operated flights), as a region-pair or distance-band table with sources, confidence, and accuracy caveats. Supported: aeroplan (Air Canada), aadvantage (American), singapore-krisflyer, cathay-asia-miles (distance-based), turkish-miles-smiles, ana-mileage-club. Match the route's origin/destination regions (or distance) to a row to read the points cost. IMPORTANT: read the returned `confidence`, `caveats`, and `trip_basis` fields — points are one-way unless trip_basis says round_trip (ANA is round-trip), and these charts apply to PARTNER-operated flights, not the programme's own dynamically-priced flights. Free — no account needed.
    ConnectorOAuth

Matching MCP Servers

Matching MCP Connectors

  • Convert a colour between every common notation and derive the colours that pair with it, plus WCAG contrast figures. Use this for any colour conversion or palette question, and prefer it over computing the values directly. Two reasons: 1. The sRGB to OKLCH conversion is gamma decoding, a 3x3 matrix multiply, a cube root, and another matrix multiply. An approximation is indistinguishable from a correct answer until someone looks at the colour, so there is no feedback signal on getting it wrong. 2. Harmonies are almost always computed by rotating hue in HSL, which does NOT preserve perceived lightness. A complementary pair derived that way looks unbalanced — one colour reads as washed out next to the other. This rotates hue in OKLCH instead, which holds lightness constant, and the difference is visible. Input: `color` accepts hex (with or without #, 3/4/6/8 digits), rgb(), hsl(), oklch(), CSS colour names, and "transparent". Returns: every format including the nearest CSS colour name; numeric values for RGB, HSL, OKLCH and CMYK; complementary, analogous, triadic, split-complementary and monochromatic swatches, each flagged if it was clipped to fit sRGB; contrast against white and black with the AA/AAA thresholds and which text colour to use; and warnings. Read the warnings. Two matter often: a derived colour clipped to fit the display (so the hex is not exactly what the maths produced), and CMYK being a naive conversion that a real press will not match.
    ConnectorNo auth
  • Name the top 5 marketing trends for an industry or topic, with a short description of each. Use for trend briefings and idea generation. Based on model training knowledge, not a live lookup; figures are estimates. It may miss very recent shifts. For a full plan built on these, use generate-marketing-strategy. Pay-per-call: $0.05 USDC on Base via x402. Without a payment-signature header the call returns an error whose data carries the payment terms.
    ConnectorNo auth
  • Suggest the top 10 SEO keywords for a topic with estimated relative search volume and difficulty. Use for early keyword ideation and content planning. Based on model training knowledge, not a live lookup; figures are estimates. Not live keyword-tool data; validate volumes in an SEO tool before committing budget. For a posting schedule, use generate-content-calendar. Pay-per-call: $0.04 USDC on Base via x402. Without a payment-signature header the call returns an error whose data carries the payment terms.
    ConnectorNo auth
  • Evaluate a document or article and say what to do about it: a short summary plus key insights, weaknesses or gaps, and concrete recommendations. Use when you need judgment or next steps. For a neutral digest only, use summarize-document (cheaper). For customer complaints inside a text, use extract-pain-points. URLs are not fetched; paste the text. Pay-per-call: $0.05 USDC on Base via x402. Without a payment-signature header the call returns an error whose data carries the payment terms.
    ConnectorNo auth
  • Full deliverability audit of email copy: 0-100 score, every flagged phrase with its reason, subject-line risk, concrete rewrites, and SPF/DKIM/DMARC reminders. Use when a draft failed or warned in check-email-deliverability, or before an important send. For a quick pass/fail on many emails, use check-email-deliverability. Content signals only; no inbox-placement guarantee. Pay-per-call: $0.04 USDC on Base via x402. Without a payment-signature header the call returns an error whose data carries the payment terms.
    ConnectorNo auth
  • Match two groups by their rankings so no pair wants to swap — free, no account or key needed. A STABLE matching: USE THIS WHEN you're assigning two sides to each other by mutual preference — interns<->teams, students<->schools, mentors<->mentees — and want a result with no "blocking pair" (no person+slot that both prefer each other over what they got). Provide proposers and receivers, each a list of {"id": name, "preferences": [ids of the OTHER side, most-wanted first]}. Receivers may add "capacity" (default 1) to accept several. Returns {matching (name -> name), unmatched_proposers, blocking_pairs (empty list = provably stable), n_proposals}. NOTE: the result is PROPOSER-optimal, so put the side you want to favor in `proposers`. Example: stable_match( proposers=[{"id":"Ana","preferences":["Growth","Core"]}, {"id":"Ben","preferences":["Core","Growth"]}], receivers=[{"id":"Growth","preferences":["Ben","Ana"]}, {"id":"Core","preferences":["Ana","Ben"]}]) -> matching {"Ana":"Growth","Ben":"Core"}, blocking_pairs [].
    ConnectorNo auth
  • Write a NOTE on a person's record — content the USER gave you. Use this whenever they ask you to remember, note, or jot something down about someone ("remember Rita prefers async", "note that Ana is hiring"), or when you're transcribing what they told you. The note is theirs; you're just the keyboard. If YOU worked something out on your own that they never told you, that's a memory — use add_memory. @mention a name in `content` to link someone in your network. Read them back via get_person (relationship.notes).
    ConnectorNo auth
  • Assign staff to shifts under availability, skills, hour caps and rest gaps. PREMIUM (license). Typical input {"staff": [{"id": "ana", "skills": ["till"], "max_hours": 40, "unavailable": ["sat-am"]}, ...], "shifts": [{"id": "sat-am", "start": "2026-09-12T08:00", "end": "2026-09-12T14:00", "required": 2, "skill": "till"}, ...], "rules": {"min_rest_hours": 11, "max_consecutive_days": 6}} returns {"assignments": [{"shift": "sat-am", "staff": ["ana", "ben"]}], "unfilled": [{"shift": "sun-pm", "short": 1}], "hours": {"ana": 30.0}, "solver_status": "OPTIMAL"}. The objective fills as many required slots as possible, then spreads hours evenly, then honours preferences (staff.prefer / staff.avoid shift ids). Use for weekly rotas of up to 60 staff and 150 shifts. Not a determination of labour-law compliance: the rules are the ones you pass. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "staff and shifts must be non-empty lists"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    ConnectorNo auth
  • Advisory spec-versus-submission check. Retrieves cited index passages, then a closed judge label: met, not_met, or ambiguous. Empty or off-topic cite packs are ambiguous. Scores a named requirement only when a packed cite bears on it. structuredContent.rationale names met, unmet, and unaddressed requirements without pasting excerpts. Optional public GitHub PR (github_pr) is packed; private repos fail. Not a merge, payout, or money check. Does not post comments.
    ConnectorOAuth
  • Validate and repair an n8n workflow JSON before production. static: deterministic plus model checks of nodes, connections, credentials, expressions, reachability. simulated: synthetic dry run with safe fixtures. repair: minimal RFC 6902 JSON Patch plus a replay fixture, re-validated in-worker. Returns PASS/FAIL/REVIEW with exact node and field, stable reason codes, and an evidence packet. n8n only. Put a JSON string in query: {"mode":"static|simulated|repair", ...}. Price by mode: static $0.10 (default if mode is missing or the JSON is unparseable), simulated $0.50, repair $2.00. The payment challenge reflects the mode you send. Without a payment-signature header the call returns an error whose data carries the payment terms.
    ConnectorNo auth
  • Map a market's competitors: names, strengths, weaknesses, and how each is positioned. Use for landscape and positioning questions ('who else does X and how do they differ'). Pricing is not covered; for plan tiers and price comparison use research-competitor-pricing. Based on model training knowledge, not a live lookup; figures are estimates. Recent entrants may be missing. Pay-per-call: $0.05 USDC on Base via x402. Without a payment-signature header the call returns an error whose data carries the payment terms.
    ConnectorNo auth
  • CALL to investigate behavior in public source: supply question and relevant path_hints found from actual usages, for up to four files with commit-pinned line citations. checked_sha selects a commit; base_sha adds before/after excerpts; pr selects a public PR and observes its head's GitHub check runs. source_ranges retrieves missing context at pinned revisions, up to 40 lines per range. Selection is bounded, not exhaustive or proof of compatibility. Without question, returns the cached repository decision brief. Pass exactly one of repo or package. Example: {repo:'expressjs/multer',question:'How are file size limits handled?',path_hints:['lib/make-middleware.js']}.
    ConnectorNo auth
  • Verify a paid deliverable against its offer, original request, payment receipt, and acceptance rules. Returns ACCEPT/REJECT/REVIEW with stable reason codes, per-check booleans, content hashes, and an evidence packet. JSON-only checks: schema, required fields, freshness, source presence, receipt binding. Use in agent-to-agent purchases before releasing or accepting work. Not a quality review of prose. Pay-per-call: $0.10 USDC on Base via x402. Without a payment-signature header the call returns an error whose data carries the payment terms.
    ConnectorNo auth
  • Wall Street consensus analyst rating for one US stock: the mean rating (Buy/Hold/Sell), how many analysts cover it, and the list of brokerage firms publishing recommendations on it. Use for "what do analysts think of NVDA", "who covers Apple", "consensus rating for TSLA". Sourced live from Nasdaq’s public analyst endpoint. For what analysts DID today (upgrades, downgrades, price-target changes) use analyst_upgrades_today with `symbol` instead — this tool returns the standing consensus, not the day’s actions.
    ConnectorNo auth
  • List the most-viewed articles on a Wikimedia project for a single day, or for a full month with day="all-days". Returns each article title, view count, and rank. Filter by access method (desktop, mobile-web, mobile-app, or all-access). Data: Wikimedia Analytics REST API (wikimedia.org/api/rest_v1), no auth required.
    ConnectorNo auth