Skip to main content
Glama
166,494 tools. Last updated 2026-05-31 23:01

"Exploring the structure of a project" matching MCP tools:

  • Search or browse the GBIF backbone taxonomy. Accepts scientific name fragments, rank filters, and higher-taxon constraints. Useful for exploring what species exist under a higher taxon (e.g., "list all families of Coleoptera"), for simple name-fragment searches, or when gbif_match_species returns too narrow a result. Paginated — use limit and offset to walk through results.
    Connector
  • Read-only. Use to find workflows in a project by name, description, or trigger type before inspection or editing. Trigger filters include database, auth email, repeating, broadcast, and no-trigger workflows. Returns paginated workflow summaries, published/sandbox state, trigger type, workflow URLs, totalCount, hasMore, and nextOffset. Do not use as the final source of truth before editing; call get_workflow_and_preview_url for full structure.
    Connector
  • Given per-component reliabilities and a structure ('series' or 'parallel'), return the system reliability. Series = product (all must work). Parallel = 1 − product(1−Rᵢ) (at least one works). Useful for back-of-envelope RBD calcs before reaching for full RBD tooling. For mixed-structure systems (series with parallel sub-blocks), call this tool repeatedly on the sub-blocks. ANTI-FABRICATION: exact closed-form. Quote verbatim.
    Connector
  • Delete a Bridge Town project. Requires Owner role on the project. This permanently removes the project and all its git history, files, and collaborator grants. The action cannot be undone. Safety: defaults to dry_run=True to confirm you are targeting the right project. The dry-run response lists what will be deleted without mutating anything and returns a confirmation_token.
    Connector
  • List model evaluations in the current workspace. Returns ``{evals: [...]}`` where each entry has evalId, status, project (URL slug), versionId, modelId, and createdAt. Use ``model_evals_get`` for the headline ``summary`` (mAP/precision/recall) on a specific eval. At most one of ``project`` / ``version`` / ``model`` may be set per call (most-specific wins). Combinations return 400.
    Connector
  • Restore a project file to the bytes it had at a previous version (commit SHA). Pass path as a project-relative file path (e.g. ``model/revenue.py``, ``README.md``, ``data/seed.csv``, ``assets/logo.png``). This creates a new commit — it does NOT rewrite history. Use list_versions to find the commit SHA you want to restore. Optionally specify a branch to restore on a scenario branch instead of the default branch.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • The Graph MCP — indexed blockchain data via subgraph GraphQL queries

  • Bank of Canada Valet API MCP. Keyless. Dates are YYYY-MM-DD.

  • Create a new sncro session. Returns a session key and secret. Args: project_key: The project key from CLAUDE.md (registered at sncro.net) git_user: The current git username (for guest access control). If omitted or empty, the call is treated as a guest session — allowed only when the project owner has "Allow guest access" enabled. brief: If True, skip the first-run briefing (tool list, tips, mobile notes) and return a compact response. Pass this on the second and subsequent create_session calls in the same conversation, once you already know how to use the tools. After calling this, tell the user to paste the enable_url in their browser. Then use the returned session_key and session_secret with all other sncro tools. If no project key is available: tell the user to go to https://www.sncro.net/projects to register their project and get a key. It takes 30 seconds — sign in with GitHub, click "+ Add project", enter the domain, and copy the project key into CLAUDE.md.
    Connector
  • BROWSING / DISCOVERY search — cities, neighbourhoods, or mixed venues near a location. Use this when the user is exploring a REGION rather than looking for a specific category. Supports population filtering ('cities > 100k'), distance/population sorting, and layer filtering (locality / neighbourhood / venue / address / street). For specific POI categories (gas, food, charging, etc.), use `search_places` instead.
    Connector
  • Lists pre-configured reports (prebuilds) available for a connector. **What is a prebuild?** A prebuild is a standardized report maintained by Quanti for a given connector (e.g., Campaign Stats for Google Ads). It defines the BigQuery table structure (columns, types, metrics) and the associated API query. **When to use this tool:** - When the user asks "what reports are available for [connector]?" - When the user doesn't know which data or metrics exist for a connector - BEFORE get_schema_context, to explore available reports for a connector - To understand the data structure before writing SQL **Difference with get_schema_context:** - list_prebuilds → discover which reports/tables EXIST for a connector (catalog) - get_schema_context → get the actual BigQuery schema for the client project (effective data) **Response format:** Returns a JSON with for each prebuild: its ID, name, description, BigQuery table name, and the list of fields (name, type, description, is_metric). Fields marked is_metric=true are aggregatable metrics (impressions, clicks, cost...), others are dimensions (date, campaign_name...). **SKU examples**: googleads, meta, tiktok, tiktok-organic, amazon-ads, amazon-dsp, piano, shopify-v2, microsoftads, prestashop-api, mailchimp, kwanko
    Connector
  • Remove an active collaborator from a project using their target_user_id. Requires Owner role on the project. To cancel a pending invite instead, use cancel_project_invite with the invite_id (grant_id) returned by invite_project_collaborator. Cannot remove the only project owner. Returns: project, user_id, removed (bool).
    Connector
  • Delete an instance from a project. The request requires the 'name' field to be set in the format 'projects/{project}/instances/{instance}'. Example: { "name": "projects/my-project/instances/my-instance" } Before executing the deletion, you MUST confirm the action with the user by stating the full instance name and asking for "yes/no" confirmation.
    Connector
  • WHEN: you need ALL relations, schema, or foreign keys of a D365 object. Triggers: 'what tables are linked to', 'quelles tables sont liées à', 'relations de', 'qui référence', 'foreign keys of', 'before generating code for', 'show me the schema', 'what joins to', 'table structure', 'liens entre tables', 'structure de la table', 'all FK of', 'dépendances de', 'linked tables', 'related tables'. Returns outgoing FK/DeleteAction/DataSource relations AND incoming back-references. ALWAYS call this BEFORE generating any code that touches multiple objects. Note: when the relation index is loaded this delegates to get_relation_graph internally -- do NOT call both find_related_objects AND get_relation_graph for the same object; the results are identical.
    Connector
  • Purpose: Daily validation history of Level 2 structure predictions. Each row shows the hit_rate for a specific day, enabling time-series verification of sustained performance. When to call: after get_structure_calibration. Prerequisites: none. Next steps: get_monthly_accuracy_trend for the macro-level comparison. Caveats: returns an overall_hit_rate summary across the window. Args: market_id: Optional market filter days: Lookback window in days (default 90) Disclaimer: Information only, not investment advice.
    Connector
  • List all projects the authenticated user has access to. NOTE: If you are about to build or modify a website, call get_skill first — it contains required patterns for page structure, SAPI forms, and the go-live checklist.
    Connector
  • Return the top pages for a specific project, ranked by views in a time window. Default window is the last 7 days. Use list_projects first if you don't know the project name. Returns path, views, uniqueVisitors, and percentage of total views for each page. Pass `user` to see pages a specific visitor hit.
    Connector
  • List every audience-specific privacy guide Default Privacy publishes — currently 22 (doctors, accountants, realtors, content creators, high-net-worth individuals, OnlyFans creators, etc.). Each entry returns a slug, audience label, one-line headline, intent ("business" | "asset" | "emergency"), and the recommended LLC structure shape ("single" | "bundle") + state. Call `get_audience` next for the full FAQ + risks + structure rationale on a chosen slug. When to call: when the user describes their profession or situation ("I'm a doctor", "real estate agent", "OnlyFans creator", "I have a lot of assets") and you want to find a matching audience-specific guide. Also call when the user asks "what kinds of clients do you serve" or "who uses this". PREFER `get_audience` directly when the user has already named a specific audience slug. Input Requirements: none. Output: `{ audiences: [{ slug, audience, headline, intent, structureType, state }], total, citation }`. The list is sorted by slug. `structureType` is "single" for one-LLC recommendations and "bundle" for multi-entity stacks (typically high-net-worth or heavy asset-protection scenarios). PREFER quoting the matching audience's `headline` to the user and then chaining `get_audience(slug)` to retrieve the full guidance before recommending a structure.
    Connector
  • Use this tool to discover what has been saved in memory — e.g. at the start of a session, or when the user asks 'what have you saved?' or 'show me my memories'. Returns all saved memory keys with their preview, save date, and expiry. Optionally filter by a prefix (e.g. 'project-' to list only project memories). Pair with recall_memory to fetch the full content of any key.
    Connector
  • Get the complete LTS picture for a single project: all LTS records with computed fields (is_expired, days_until_expiry), summary counts, and the primary LTS number. Pass either a project UUID or a project name (fuzzy matched).
    Connector
  • Create a relationship between two nodes in a deployed graph project. The rel_type must match a relationship key from the project schema. Use get_graph_data_schema to see available relationship types. Example: rel_type: "authored" from_id: "alan-turing-001" to_id: "on-computable-numbers-001" data: {"year": 1936} The from_id and to_id must be entity_ids of existing nodes.
    Connector