Skip to main content
Glama
650,462 tools. Updated 2026-10-13 10:38

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

  • 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.
    ConnectorNo auth
  • Returns the organization's development standards: coding conventions, project structure, and framework-specific rules. Read-only. Call it before writing or reviewing code, so the result follows this organization's rules rather than general defaults. Call it first without a section to get an index of available sections, each with a note on what it covers, then call again with one section id copied from that index; inventing a section id returns a not-found error naming that step. Request only the sections a task needs - the full content of one section can be long. The framework argument is deprecated: use section with the "framework:" prefix instead. It returns prose rules, not data - use get_style_tokens for visual values and get_component for component APIs.
    ConnectorNo auth
  • Purpose: return the rCB and virgin carbon black price benchmark structure - the virgin N550 series as anchor, the rCB band expressed as 25-40% of that anchor, feedstock prices, international references, regional spreads, grade-level bands and cost structure. Guidelines: leave product and section empty for the full set; narrow with section='rCB' / 'feedstock' / 'international' / 'cost'; pair with get_elt_price_index for feedstock indices and get_rcb_index for the layered index series. Limits: reference bands and relative structure only - no exchange quote and no trading recommendation; ELT feedstock absolute prices are deliberately not published; every figure is a range, never a single transactable value. Ex: get_price_benchmark(section='rCB'), get_price_benchmark(product='N330', language='en'), get_price_benchmark(section='cost', response_format='json').
    ConnectorNo auth
  • Use first when a buyer is exploring LeadProof without supplying workflow data. Returns the official no-purchase sequence: buyer guide, fictional example audit, browser-only calculator, public workflow tests, and no-card trial. For a scored workflow diagnosis, use audit_lead_workflow; for replay testing, use get_leadproof_replay_trial; for paid checkout, use get_leadproof_checkout only after authorization.
    ConnectorNo auth
  • Archive a project (reversible shelve) — frees a project slot in-tool. Stops any in-flight machine, then flips the project to `archived`: it drops out of the per-tier project cap (freeing a slot for a new project) and the loop stops dispatching it, but the project + its history are kept and can be restored from the dashboard project page. Stopping a machine DESTROYS the running process state — restoring the project later cannot bring that execution back, so this is destructive despite being reversible. A replay on an already-archived project changes no row, but is not idempotent end to end. This is preferable to `delete_project` unless the project must be gone. Owner-scoped (an MCP key is owner-only); a project not in the workspace 404s.
    Connector
    Destructive
    No auth
  • Call only after example_prompts and after you have completed prompt drafting/approval (non-tool step). PlanExe turns the approved prompt into a strategic project-plan draft (20+ sections) in ~10-20 min. Sections include: executive summary, interactive Gantt charts, investor pitch, project plan with SMART criteria, strategic decision analysis, scenario comparison, assumptions with expert review, governance structure, SWOT analysis, team role profiles, simulated expert criticism, work breakdown structure, plan review (critical issues, KPIs, financial strategy, automation opportunities), Q&A, premortem with failure scenarios, self-audit checklist, and adversarial premise attacks that argue against the project. The adversarial sections (premortem, self-audit, premise attacks) surface risks and questions the prompter may not have considered. Returns plan_id (UUID); use it for plan_status, plan_stop, plan_retry, and plan_file_info. To track progress, poll plan_status at reasonable intervals (e.g. every 5 minutes). Optionally, run `curl -N <sse_url>` in a background shell as a completion detector — the stream auto-closes on terminal state (completed/failed/stopped). If you lose a plan_id, call plan_list to recover it. If the same prompt + model_profile is submitted by the same user within a short window, the existing plan is returned (with deduplicated=true) instead of creating a new one. If you are unsure which model_profile to choose, call model_profiles first. If your deployment uses credits, include user_api_key to charge the correct account. Common error codes: INVALID_USER_API_KEY, USER_API_KEY_REQUIRED, INSUFFICIENT_CREDITS.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    A
    quality
    C
    maintenance
    Analyzes Python project structure by exploring directory trees, extracting outlines from Python and Markdown files, and inspecting OpenAPI specifications.
    5
    MIT

Matching MCP Connectors

  • SDMX Structure MCP — dataflow dimensions and code lists for any SDMX 2.1

  • Extrait des champs structures (texte, nombre, date) depuis un texte libre.

  • [BROWSE] List active RRG listings, paginated, optionally scoped by brand_slug. Use when exploring the catalogue without a specific item in mind. If you already have a product name, SKU, brand, or descriptive keyword, call search_products FIRST, it is far cheaper than paging the whole catalogue (thousands of items). Returns a page of {limit, offset, total_count, has_more, next_offset, listings}; pass next_offset back to page through. Each listing has title, price in USDC, edition size, and remaining supply. Live on-chain minted count is in get_drop_details, not here. Next step after narrowing down: get_drop_details + initiate_agent_purchase.
    ConnectorNo auth
  • [BROWSE] List active RRG listings, paginated, optionally scoped by brand_slug. Use when exploring the catalogue without a specific item in mind. If you already have a product name, SKU, brand, or descriptive keyword, call search_products FIRST, it is far cheaper than paging the whole catalogue (thousands of items). Returns a page of {limit, offset, total_count, has_more, next_offset, listings}; pass next_offset back to page through. Each listing has title, price in USDC, edition size, and remaining supply. Live on-chain minted count is in get_drop_details, not here. Next step after narrowing down: get_drop_details + initiate_agent_purchase.
    ConnectorNo auth
  • Correct the name of a project: the folder keeps its id, its canon, its trackers, its surfaces and its logbook, and the name shown is the only thing that changes. Names are unique per account: a name another project already goes by answers project_exists with that project, so read it back and settle another name with the user. Case, accents and spacing do not make two different names, which is why a project can always take back its own capitalisation. Sending the name it already carries answers the same, and a project filed away renames like any other. Use it for the name of the folder; the wording of the brand itself is the canon, and it moves with update_project_canon.
    ConnectorNo auth
  • Creates a task in OmniFocus on this Mac. Needs OmniFocus Pro (the free tier blocks automation). Without `project` the task goes to the inbox. `project` must be the exact name of an existing project: if no project has that name the call fails with an error instead of falling back to the inbox — check the name with list_omnifocus_projects first. Called without confirm it returns a preview; pass confirm=true to create. Returns the task id.
    ConnectorOAuth
  • List all projects the authenticated user has access to. Returns the id, name and subdomain of each project. At the start of a conversation prefer get_started: it includes this list plus the project to build in and the next call.
    ConnectorAPI key
  • Point VARRD's autonomous AI in a direction and let it discover edges for you. Give it a topic and it draws from one of the most comprehensive market structure knowledge graphs ever built — containing ideologies and theories, not statistics — so it generates genuinely novel hypotheses rather than overfitting to what already worked. BEST FOR: Exploring a space broadly. Give it 'momentum on grains' and it might test wheat seasonal patterns, corn spread reversals, or soybean crush ratio momentum. It propagates from your seed idea into related concepts you might not think of. Returns a complete result — edge or no edge, stats, trade setup. Each call tests ONE hypothesis through the full pipeline (~$0.25/idea). Call again for another idea. Use 'varrd_ai' instead when YOU have a specific idea to test and want full control over each step.
    ConnectorNo auth
  • Creates a new, empty question bank for the given Riddle type ("Quiz" or "Poll"). Add items with question_bank_item(action: "add"), then reference the returned "id" as "questionBankId" on a QuestionBank block of a riddle_builder_create call of the matching "type" - a bank created for "Quiz" can only be referenced from a Quiz, never a Poll, and vice versa. A bank lives in one project and can only be referenced from Riddles of that same project, so pass the projectId of the project the Riddle belongs to; omitting it creates the bank in the project the API key is scoped to. Needs full access: riddle://reference/concepts/access.
    ConnectorNo auth
  • Creates a new, empty question bank for the given Riddle type ("Quiz" or "Poll"). Add items with question_bank_item(action: "add"), then reference the returned "id" as "questionBankId" on a QuestionBank block of a riddle_builder_create call of the matching "type" - a bank created for "Quiz" can only be referenced from a Quiz, never a Poll, and vice versa. A bank lives in one project and can only be referenced from Riddles of that same project, so pass the projectId of the project the Riddle belongs to; omitting it creates the bank in the project the API key is scoped to. Needs full access: riddle://reference/concepts/access.
    ConnectorNo auth
  • Render a background as SVG or PNG. Deterministic: the same structure, options and seed always give the same image, so store the returned seed. Returns a permanent, cacheable image URL you can use directly in <img>/CSS, plus an inline PNG preview. Call describe_background first to learn which shape options the structure honours.
    ConnectorNo auth
  • Create a knowledge/documentation entry for a project — a convention, workflow note, metric definition, reference guide, or ADR to persist across sessions and be surfaced back to you (or other agents) as context. Call list_knowledge_docs first to check a similar doc doesn't already exist: there is no update tool yet, so calling this again produces a duplicate, not an overwrite — delete_knowledge_doc the stale one first if you need to replace it. Cannot target "__global__" (read-only). ADRs (type "adr") are Architecture Decision Records — one specific architectural decision, not a general note. content MUST include a "## Context", "## Decision", and "## Consequences" section (any other structure is rejected) — write Context as the problem/forces at play, Decision as specifically what was decided (concrete enough that a future agent can check compliance against it), and Consequences as what becomes easier/harder as a result. ADRs are never deleted once accepted — to reverse one, create a new ADR and set the old one's status to "superseded" (via update_knowledge_doc's adrStatus) with supersededBy pointing at the new one's id. An accepted ADR gets synced into a coding-agent repo automatically the next time a task runs there (see repoUrl below for which one), and is injected into every agent's context for that project going forward — so only record a decision here once it is actually decided, not while still exploring options (use adrStatus "proposed" for that, the default).
    ConnectorOAuth
  • Get the structure (Data Structure Definition) of one ILOSTAT dataset: its ordered dimensions and, for each, the valid codes. Use this to learn how to build the dot-separated SDMX key for get_data. The key positions correspond to the dimensions in order; an empty position is a wildcard. Common dimensions are REF_AREA (ISO3 country code, e.g. "USA", "FRA"), FREQ (A=annual, Q=quarterly, M=monthly), SEX, AGE, and MEASURE. Always call this before get_data. Example: dataflow_structure({ dataflow_id: "DF_SDG_0852_SEX_AGE_RT" }).
    ConnectorNo auth
  • Discover curated topics (2,184 entries with aliases). USE WHEN: planning a multi-round quiz, exploring "what is available about X", showing topic browser. Sorted by count DESC, slug ASC. Cursor-paginated. INPUTS: q (substring on label/alias), kind (tag|subcategory), cursor, limit (max 500).
    ConnectorNo auth
  • Discover region codes used by the catalog. **Cultural affinity** — a question is tagged with a region if residents of that country, or members of that cultural/religious group, are statistically more likely to know the answer (NOT geography of the subject). USE WHEN: planning a quiz targeting users from a specific country or cultural background, exploring "what regions are represented". OUTPUT: array of {code, kind, label, count} sorted by count DESC. INPUTS: lang (en|pl), q (substring on code/label), kind (country|cultural), cursor, limit (max 500). Pair with quizbase_random or quizbase_list using `regions:[...]` to fetch matching questions.
    ConnectorNo auth
  • Create a new project in a workspace. If a project with the same name already exists in the workspace, returns the existing project instead of creating a duplicate — check the `created` field in the response to tell the two cases apart.
    ConnectorOAuth
  • Check whether a GeoJSON file/string is valid — catches broken geometry, malformed structure, self-intersections, and out-of-range coordinates before you try to use the file elsewhere (e.g. "is this GeoJSON valid", "why won't my GeoJSON load", "lint my GeoJSON", "check topology errors"). Validates RFC 7946 structure, topology, and WGS84 coordinate ranges. Returns a JSON report: {valid, errors, warnings, stats}.
    ConnectorNo auth