Skip to main content
Glama
471,413 tools. Updated 2026-08-24 00:08

"Two agents working simultaneously" matching MCP tools:

  • Permanently delete one of the caller's API keys. DESTRUCTIVE — agents using the deleted key will receive auth errors immediately. The Blueprint a key was tied to (if any) is NOT affected; only the credential is revoked. To delete a Blueprint and all its keys, use delete_blueprint. The target key can be specified two ways: - As the full key string (gai_...). - As a key_id (SHA-256 hash from list_api_keys).
    Connector
  • Generate a new API key for your agent. The full plaintext key (m2m_...) is returned ONCE — store it securely immediately; it cannot be retrieved later (we only keep its hash). Use keyName to identify the key's purpose (e.g. 'production', 'staging'). Multiple keys can be active simultaneously for zero-downtime rotation. Requires: an existing API key from register_agent. Next: switch your integration to the new key, then revoke_api_key on the old one.
    Connector
  • OMEGA — claim ONE seat in a lobby, identified by lobby_id from list_omega_lobbies, for that lobby's stated entry fee. This is a single, bounded, operator-authorized entry (the fee is fixed and moves once) — NOT an open-ended loop; confirm the cost with your operator first. Same two-call handshake as submit_entry: call once for a partial-signed enter_contest transaction (pending_tx), sign + broadcast it, then call again with transaction_signature to confirm your seat. Entry-Vault-enrolled agents join in ONE call (no signing). The entry fee moves once, at join — the six round submissions are free.
    Connector
  • Exchange two players' places. Fixed-pair doubles: swaps partners between two pairs permanently (name one player from each pair). Americano/mexicano: pass `round` to swap two players' places in ONE unplayed round — the courtside patch for a late arrival, an injury, or two friends who want a game together. One of them may be sitting that round, which is how you put a late arrival on court. Preview first, confirm to apply: the preview names any partnership or meeting the swap would repeat. Results already played never move.
    Connector
  • Return the catalog of paired models — concrete real-world systems that live in two ChiAha sandboxes simultaneously, one for dynamics (DES via ReliaSim) and one for statistics (distribution fitting + validation via ReliaStats). Today: a single paired model — the bottling line. Returns canonical model IDs + cross-MCP routing metadata (which ReliaSim chapter, which ReliaSim MCP tools, which ReliaStats mode consumes which file shape). Use when a user asks about cross-MCP workflows, paired sandboxes, or the bottling-line example. ANTI-FABRICATION: this is a soft-reference catalog — to actually run a simulation, the LLM client calls ReliaSim's MCP tools directly.
    Connector
  • Locks in the CURRENT terms of the negotiation exactly as they stand and creates a permanent, immutable Contract between the two agents. Only the agent whose turn it is may accept — meaning you can only accept terms the other agent just proposed to you, never your own last offer. This cannot be undone or edited afterward; use deal_propose_terms instead if you want different terms.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Find every window when the given planets occupy the same rashi (sign) simultaneously — conjunction-class questions over ±5000 years, instant. Example questions: "when are Guru and Shani next together in Kumbha?" (the ~60-year social-cycle conjunction), "when were Guru, Shani and Mangala last in one sign?", "were all planets really in one rashi at the Kali Yuga epoch (Feb 3102 BCE)?", "great conjunctions in the 1st millennium". Resolution is the rashi (30°) — for exact-degree conjunctions treat these windows as candidates. Including Chandra gives many short (~2 day) windows; omit it for long-period questions. Args: grahas: Two or more of: Surya, Chandra, Mangala, Budha, Guru, Shukra, Shani, Rahu, Ketu. start_date, end_date: YYYY-MM-DD, negative years allowed. rashi: Optional sign filter — Vedic (Mesh..Meen) or western (Aries..Pisces) name, or 1..12. Omit = any shared sign. ayanamsa: "Lahiri" (default) or "Sayan". max_results: Cap (≤100); response flags truncation.
    Connector
  • Which caption openings actually earn views. Pass account_id or tag to measure YOUR accounts against their own median (0.001 USDC). Pass niche to report what is working in that niche across TikTok, needing no posting history — the answer for a brand-new account (0.05 USDC; tiktok_niches lists them, free). The two are never blended. Pass caption to classify a draft before posting. Paid per-action via x402 — the 402 challenge carries the exact price for the arguments you sent.
    Connector
  • OMEGA — claim ONE seat in a lobby, identified by lobby_id from list_omega_lobbies, for that lobby's stated entry fee. This is a single, bounded, operator-authorized entry (the fee is fixed and moves once) — NOT an open-ended loop; confirm the cost with your operator first. Same two-call handshake as submit_entry: call once for a partial-signed enter_contest transaction (pending_tx), sign + broadcast it, then call again with transaction_signature to confirm your seat. Entry-Vault-enrolled agents join in ONE call (no signing). The entry fee moves once, at join — the six round submissions are free.
    Connector
  • Signed verified-registry audit. Fetches a public A2A agent registry (default a2aregistry.org) and re-grades it: how many of its 'healthy' agents carry a cryptographically-signed card, how many declare no auth, how many fail conformance — the trust signals the registry stamps over. action='probe' also live-tests a bounded sample with the two-challenge hollow-detector and returns the ALIVE/HOLLOW/DEAD breakdown. Ed25519-signed, timestamped, recomputable. Use to vet an agent directory before trusting its listings, or to find a real agent to transact with. (price: $0.05 USDC, tier: metered)
    Connector
  • Share a verified finding back to the docs corpus so the next agent can find it. Use AFTER solving a non-trivial problem to record what would have saved you time: a gotcha, a working parameter combo, an undocumented constraint, a relationship between two natives that isn't obvious. Other agents will find this via `semantic_search` (findings are merged into default results; `category: 'learnings'` returns only findings). WHEN to use: - You burned multiple iterations on something not in the docs. - You discovered an undocumented quirk (param order, hash collision, framework export that isn't in `vorp`/`rsgcore`). - You verified that a specific combination works (e.g. native A + flag B for behavior C). WHEN NOT to use: - The information is already in the docs (verify with `semantic_search`/`grep_docs` first). - You're guessing — only contribute verified findings. - It's project-specific (your repo's auth flow, your DB schema). Keep it general to RedM/RDR3. Keep `title` short and searchable. `body` should explain WHY, not just WHAT — context, the trap, the fix.
    Connector
  • Get the current certified ECB reference rate between two supported currencies — useful for converting shipping costs quoted in different currencies (USD, EUR, INR, SGD, CNY, JPY, and the rest of the official ECB daily series). Use this to normalize costs from different carriers/countries to a common currency for comparison. The official publication is updated on ECB working days; unsupported currencies fail closed. FREE — no payment required. Returns: { rate, from, to, source, fetched_at, cache_age_minutes }
    Connector
  • Agent-to-agent messaging via Telegram — the fastest real-time channel between agents. Two modes: (1) Direct DM: provide target_agent_id to deliver a private message to that agent's operator on Telegram (they must have registered their Telegram via /api/agent/set-contact). (2) Group broadcast: omit target_agent_id to post to @x711criptic, the live x711 agent community on Telegram — all operators monitoring the group see your message instantly. Requires API key. Returns: { delivered, method: 'direct'|'group', to, note }. Cost: $0.02.
    Connector
  • 3-parallel-source search + Groq synthesis → one authoritative answer with cited sources. Use instead of web_search when you need a definitive answer, not just links. Runs HackerNews + Wikipedia + DuckDuckGo simultaneously, then Groq distills into a single confident reply with source attribution. $0.05. Requires API key.
    Connector
  • 3-parallel-source search + Groq synthesis → one authoritative answer with cited sources. Use instead of web_search when you need a definitive answer, not just links. Runs HackerNews + Wikipedia + DuckDuckGo simultaneously, then Groq distills into a single confident reply with source attribution. $0.05. Requires API key.
    Connector
  • Counts the number of working days between two dates (inclusive), excluding Saturdays, Sundays, and all 10 Portuguese national public holidays. Returns { start_date, end_date, working_days: number }. Use when calculating Portuguese invoice payment deadlines (30/60/90 days), legal notice periods, project milestones, SLA response times, or any business process governed by Portuguese working days. Input dates must be in YYYY-MM-DD format.
    Connector
  • Move the caller's org to Pro ($19/mo flat, 10 agents, 20 members, 200 workspaces, 5k rows per workspace) or Scale ($49/mo flat, 30 agents, 60 members, 1,000 workspaces, 50k rows per workspace). The bill doesn't change as you add agents. If the org has no card on file, returns a Stripe Checkout URL for the human. If a card exists, a live plan switch (Pro ↔ Scale) is consent-gated. Two consent surfaces, you pick via `mode`: (1) `chat` (default): FIRST call returns { status: 'confirmation_required', confirm_token, message, expires_in }; surface the message to your user and re-call within 60s with `confirm_token` set. (2) `web`: FIRST call returns { status: 'approval_required', approval_url, polling_url, expires_at }; print the approval_url in chat for your user to click and approve in their browser, then poll `polling_url` for the result. No-card and same-plan paths execute on the first call (no money changes hands).
    Connector
  • Ask the whole network a question AS YOU. Real people's agents who actually know your topic answer from THEIR own memory (not a web search / not the model's guess). Returns a question id (qid) + a status message; then call check_answers(qid) to read replies as they arrive — a good answer usually lands in a minute or two (it also reaches the asker's inbox).
    Connector
  • Search REGISTERED onchain agents in the Sato Agent Registry — running 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. 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. Returns (json): { total, agents: [{ sato_agent_id, slug, name, description, agent_type, chains_supported, stack, payment/x402 metadata, verification_status, profile_url, manifest_url }] }. Read-only. Example: { chain: "Base", x402_only: true }
    Connector
  • Span mode (from+to): business days between two dates, exclusive of the start day, inclusive of the end day. Add mode (days, optional date): the date N business days away. Optional holiday jurisdiction or custom calendar, and a selectable working week.
    Connector