Skip to main content
Glama
742,096 tools. Updated 2026-11-04 12:32

"Information about agents or agent-related topics" matching MCP tools:

  • Get information about the organization your agent is linked to. WHEN TO USE - You want to know which organization your agent is operating under. - You need to list the members of your linked org (e.g., to decide which member should review a deliverable). WHEN NOT TO USE - To create, update, or delete organizations — those actions require human authentication via the REST API (POST /api/v1/organizations, PATCH /api/v1/organizations/{slug}, etc.). BEHAVIOR - Read-only. Auth required: agent API key. Rate-limited to 60 req/min. - Returns an error if your agent is not linked to any organization (agents.org_id IS NULL). - action='get_my_org': returns org name, slug, tier, owner, and member count. - action='list_members': returns human_id and role for each member. WORKFLOW - Check your org membership before referencing org context in deliverables or communications. - To link your agent to an org, a human admin must call POST /api/v1/organizations/{slug}/agents.
    ConnectorNo auth
  • Use this when the user asks what Alicia or digitalgarden.si has written about a subject (for example Houdini, Three.js, WebGPU, glTF/USD, Gaussian splats, AI coding agents, or the garden itself). Ranks published notes by keyword match on title, topics, summary and full text, in English and Chinese, and returns short cards (no full text). Follow up with get_article to read one. Do not use it for general web search, news, or topics unrelated to Alicia's published notes. An empty articles array means no published note matches. Scores are relative to this query and catalog, not confidence percentages; check titles and read the full note before presenting a match as relevant. Every result includes canonicalUrl and author Alicia (Person @id https://digitalgarden.si/#alicia). Cite the canonical URL when quoting. digitalgarden.si is an interactive 3D garden, not a knowledge-base wiki.
    ConnectorNo auth
  • Use this when the user asks what Alicia or digitalgarden.si has written about a subject (for example Houdini, Three.js, WebGPU, glTF/USD, Gaussian splats, AI coding agents, or the garden itself). Ranks published notes by keyword match on title, topics, summary and full text, in English and Chinese, and returns short cards (no full text). Follow up with get_article to read one. Do not use it for general web search, news, or topics unrelated to Alicia's published notes. An empty articles array means no published note matches. Scores are relative to this query and catalog, not confidence percentages; check titles and read the full note before presenting a match as relevant. Every result includes canonicalUrl and author Alicia (Person @id https://digitalgarden.si/#alicia). Cite the canonical URL when quoting. digitalgarden.si is an interactive 3D garden, not a knowledge-base wiki.
    ConnectorNo auth
  • Check Roamzy API status, including agent pause flags. Agents MUST call this before purchase attempts and back off if `purchases_paused=true`.
    ConnectorNo auth
  • Check this connection's authenticated contributor identity, operator boundary, scopes, expiry and write_epoch before a contribution, or when explicitly asked about connection identity. Not required for anonymous search or fetch. Read-only; returns authenticated:false without a valid credential. Same-operator agents are not independent reproductions.
    ConnectorNo auth
  • Return the workspace's knowledge graph: topics, links and clusters. Use it to draw or reason about the overall shape of the brain (which topics are hubs, how areas connect), not to read content: for page text use ``get_page``, for code dependencies use ``impact``. It takes no arguments and can be large. Returns ``{nodes, links, communities, stats}``, the graph the app's Map shows, with pages you cannot open left out, or ``{error}`` when no graph has been built for this workspace yet. It costs no AI tokens.
    ConnectorAPI key

Matching MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    An MCP server that provides information about Utkarsh, including bio, skills, work experience, and portfolio projects, accessible via local stdio or remote HTTP with OAuth.
    6
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Provides AI agents with real-time trending topics from Weibo, Baidu, Zhihu, Google Trends, and HackerNews/StackExchange community intel, enabling content and marketing agents to stay aware of current conversations before creating content.
    MIT

Matching MCP Connectors

  • The topics in a set of documents in one call, with each document's topic mixture. Nothing stored.

  • About Bureau, the self-hosted office for AI agents: overview, FAQ search, roadmap, install.

  • Search the PUBLIC Awareness knowledge graph — 1,000+ sourced scientific papers. Use this when the user (especially a researcher or a research agent) asks for peer-reviewed findings: "latest evidence on X", "highly-cited papers about Y", "what does the literature say about Z". This is NOT a memory tool — it does not read the user's private memory, and it needs no per-user API key, so it works even when Awareness memory is not configured (the MCP connection itself still needs its own token). Coverage: condensed-matter, quantum-information, materials, machine-learning, renewable-energy, chemistry, biology, medicine, neuroscience, computer-science (2022-2026, cited >= 50), plus a business supply/demand domain. What comes back (anonymous preview mode): title, snippet (preview), confidence, source_ref (DOI), citation_count, domain/topic, and a detail page URL. Full content is NOT in the preview — tell the user it is paid retrieval via POST /api/v1/public/retrieve with an API key (see https://awareness.market/en/knowledge for the KaaS product). Args: query: Natural-language research question or keywords (2-1000 chars). domain: "science" (default) or "business". topic: Optional sub-topic slug, e.g. "medicine", "condensed-matter", "supply-chain". Empty = search all topics in the domain. top_k: Max results, 1-20 (default 5; anonymous callers are capped at 3). include_graph: When true, also return same-topic related items. Returns: {"results": [{id, title, snippet, confidence, source_ref, citation_count, domain, topic, url}], "related": [...], "total": int, "mode": str} `mode` is "preview" (anonymous) or "full" (authenticated).
    ConnectorNo auth
  • List the specialist agents in the product/app the request is scoped to. Returns a summary (count, brief one-liner, and a list of {id, name, status, type, role, one-line icp_summary}). Internal agent types are mapped to product-facing roles such as lead_finder. Full ICP filters / config are collapsed to a one-liner — call get_agent (later) to load full detail. Use this to ground questions like 'how many specialist agents do I have?' or 'which Lead Finder agents are active?'.
    ConnectorOAuth
  • Ranked related listings with per-item reasons. Seed with listing_id (same category or domain, shared tags, agents that used the seed also used these), or call authenticated with no seed for picks based on your recent usage. Not a keyword search: use search_catalog for that.
    ConnectorNo auth
  • Get care plan material for a specific NANDA-style nursing diagnosis: its definition, related factors (the "related to" clause), defining characteristics (the "as evidenced by" clause), SMART goals, interventions, and the conditions where it is a priority. Use when a nursing student asks about a diagnosis rather than a disease, for example "risk for infection", "acute pain", "impaired gas exchange", "ineffective coping" or "risk for falls", or asks how to write a three-part diagnosis or an AEB statement. Educational reference, not medical advice.
    ConnectorNo auth
  • USE WHEN you need a RUNNING agent to work with, hire or pay (not a tool to build one with) and want to see who registered it, on which chain, and whether it accepts payment. NOT FOR tools to build an agent from (use onchain_agent_search_resources instead), one agent's full manifest (use onchain_agent_get_agent_passport with a slug from here), or a ranked pick for a task (use onchain_agent_route_agent). RETURNS (json): { total, agents: [{ sato_agent_id, slug, name, description, agent_type, chains_supported, stack, payment/x402 metadata, verification_status, profile_url, manifest_url }] }. Searches the Sato Agent Registry: agents whose creators registered them for a Sato Agent Passport (distinct from the resource directory, which lists the things agents are built FROM). Filter by free-text query, chain, agent_type, or x402_only. Only human-review-listed agents are returned. Registry agents come first; when the registry has no match for a query, matching agent-type directory listings come back in listings[] with kind "listing" (not passports), and total counts both. A query that names a brand ("aixbt", "olas") also returns brands[]: the identities someone declared for it (ERC-8004 ids, wallets, builder codes), each saying who declared it (the brand, the platform that lists it, or the registrant); brands are not registry results and are not counted in total. Read-only. This is the Sato Agent Registry only: agents whose builders registered them with Sato Hub, a small set. It does not search agents registered onchain under ERC-8004, so an empty answer here says nothing about them. For those, call onchain_agent_get_agent_economy with venue "erc8004" (measured counts by chain), or see https://satohub.ai/agent-economy/erc8004 and https://satohub.ai/erc8004/<chain>. Trust rule: registration is self-reported by the creator; verification_status distinguishes Self-Reported from evidence-reviewed Verified/Audited. Nothing here implies safety or performance. Example: { chain: "Base", x402_only: true }
    ConnectorNo auth
  • 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. It covers a topic cluster in one call, for content planning across related pieces. 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
  • Google Trends related topics for a keyword. Returns the topics and named entities associated with a keyword in a given country, as top topics scored 0-100 relative to each other and rising topics with percentage growth, each carrying its entity type. Google Trends topic discovery for market research and content planning. [$0.03/call]. Params — keyword: the search term; geo: ISO-3166 alpha-2 country code, e.g. US, GB, DE, JP (213 countries supported); timeframe: time window. Each response reports its own bucket size in `granularity`: past_30_days and past_90_days return a daily series, past_12_months and past_5_years weekly, windows under a day hourly (2004_present|past_12_months|past_30_days|past_4_hours|past_5_years|past_7_days|past_90_days|past_day|past_hour) Example params: {'keyword': 'bitcoin', 'geo': 'US'}
    ConnectorNo auth
  • Read-mostly first step before you start any piece of work or touch a contested resource. Returns signal GREEN, AMBER or RED with the reasons in words, how many other agents hold or recently looked at the same key, the marks earlier agents left on it, live facts from the venue for Taskmarket tasks and GitHub issues (open or closed, reward, funding, crowd), and, when you pass reward_usd and effort_usd, the expected value of doing it. Use look when you are deciding whether to start; use claim once you decided to start; use check_spend for a decision about money, not about work. Side effect: when you pass agent, the crossing remembers for fifteen minutes that you looked, so others see the crowd; nothing else changes and no lease is taken. Safe to repeat.
    ConnectorNo auth
  • Returns FARA registrations — US persons and firms registered with the DOJ as agents of a foreign principal under the Foreign Agents Registration Act. Use this when the user asks about: who is a registered foreign agent, which US firms work for a particular foreign government, recently-registered foreign agents, or to add a 'foreign- influence' flag to a lobbying firm, law firm, or PR firm. Each record is one registrant ↔ foreign-principal relationship — a registrant representing three foreign principals appears as three records. The single highest-signal filter is foreign_principal_country: foreign_principal_country='CHINA' → every US agent acting for a Chinese principal Source: efile.fara.gov (DOJ National Security Division). v1A covers ACTIVE registrations. The registrant↔principal linkage is included; per-document filing detail and compensation figures are not — follow source_url to FARA eFile for those. Cross-source pairing pattern: FARA + get_lobbying_filings — FARA is foreign-principal representation; LDA is domestic lobbying. A firm in both is lobbying Congress on behalf of a foreign government. FARA + get_fec_contributions — foreign-agent firms whose people also make political contributions. FARA + get_congressional_trades — influence-and-trades overlay. Identifier: registration_number is the FARA registration number. has_foreign_principal=false records are registrants with no currently- active foreign principal (still queryable as registered agents). History: registrations that LEAVE DOJ's active list are kept with status:'terminated' (+ termination_observed_date) rather than deleted — a terminated registration is still real history. Default queries return BOTH; filter status:'active' for the current roster only.
    ConnectorNo auth
  • Search verified Capable how-to/setup/troubleshooting articles verbatim with citations, or fetch article_key; offer related topics. Use get_context/search_records for CRM data. Answer ONLY from returned articles and cite titles; never guess product behavior from memory. If confident:false or no article answers, say no verified answer is available and offer hello@capable.run as backup. Call with diagnostics:true, before saying their mail or calendar isn't connected: both connect to Capable, apart from any connector this chat has. Checks saved connection/import/agent settings. Diagnostics show setup facts, not live provider health. When to use: Questions about how Capable itself works, or checking saved connection status. Example: How do I set up a booking link in Capable?
    ConnectorAPI key
  • Costs one of the agents' shared daily dates (once a date; never your weekly dates or tokens). On a two-agent date where the other agent has been quiet 3+ minutes on its move: the show's model performs that character's remaining turns, and you keep playing yours. Rarely needed: it happens on its own the next time either agent reads or advances the date (get_own_date_step, wait_seconds, my_status), unless the agents' daily budget is spent. get_own_date_step says how long they've been quiet (quiet_minutes) and can_hand_over.
    ConnectorNo auth
  • Signal that this agent session is complete. Flips the underlying AiConversation agentStatus to ENDED so the human-side Settings → Agents UI shows the session as terminated. Optional reason string (1-500 chars) is captured for audit. Idempotent: calling again returns the existing terminal status without changing it. Honest agents call this when they've finished their assigned work or are about to disconnect; humans can also revoke the PAT, which is more forceful but achieves the same lifecycle outcome. Any task leases this session still holds are handed back, so the tasks become available to other agents immediately rather than after the lease expires.
    ConnectorOAuth
  • Costs one of the agents' shared daily dates (once a date; never your weekly dates or tokens). On a two-agent date where the other agent has been quiet 3+ minutes on its move: the show's model performs that character's remaining turns, and you keep playing yours. Rarely needed: it happens on its own the next time either agent reads or advances the date (get_own_date_step, wait_seconds, my_status), unless the agents' daily budget is spent. get_own_date_step says how long they've been quiet (quiet_minutes) and can_hand_over.
    ConnectorNo auth
  • Ask Limpide for maths exercises this server does not have yet, or give one line of feedback on an exercise. Use it when generate_exercises has no topic for what the tutor needs. Limpide reads the requests each morning to choose the next topics, and promises nothing; the answer lists the topics that exist today. Never include a student's name, work or answers: name the topic, the level and, if useful, one line about what is missing.
    ConnectorNo auth
  • Flag a Hive post (hvp_...) or reply (hvr_...) that breaks the rules: spam, off-topic, harmful, instructions (it tries to give agents commands), personal-data or other. A moderator reviews every flag within a day; flags from 2 different agents hide the item until then. Not for disagreeing: reply instead. Needs a verified agent key and the same karma as voting. Limit: 10 flags per 24 hours.
    ConnectorNo auth