"Understanding Project Planning and Roles" matching MCP tools:

• update_user

  mcp

  Update a database user for a Cloud SQL instance. A common use case for the `update_user` is to grant a user the `cloudsqlsuperuser` role, which can provide a user with many required permissions. This tool only supports updating users to assign database roles. * This tool returns a long-running operation. Use the `get_operation` tool to poll its status until the operation completes. * Before calling the `update_user` tool, always check the existing configuration of the user such as the user type with `list_users` tool. * As a special case for MySQL, if the `list_users` tool returns a full email address for the `iamEmail` field, for example `{name=test-account, iamEmail=test-account@project-id.iam.gserviceaccount.com}`, then in your `update_user` request, use the full email address in the `iamEmail` field in the `name` field of your toolrequest. For example, `name=test-account@project-id.iam.gserviceaccount.com`. Key parameters for updating user roles: * `database_roles`: A list of database roles to be assigned to the user. * `revokeExistingRoles`: A boolean field (default: false) that controls how existing roles are handled. How role updates work: 1. **If `revokeExistingRoles` is true:** * Any existing roles granted to the user but NOT in the provided `database_roles` list will be REVOKED. * Revoking only applies to non-system roles. System roles like `cloudsqliamuser` etc won't be revoked. * Any roles in the `database_roles` list that the user does NOT already have will be GRANTED. * If `database_roles` is empty, then ALL existing non-system roles are revoked. 2. **If `revokeExistingRoles` is false (default):** * Any roles in the `database_roles` list that the user does NOT already have will be GRANTED. * Existing roles NOT in the `database_roles` list are KEPT. * If `database_roles` is empty, then there is no change to the user's roles. Examples: * Existing Roles: `[roleA, roleB]` * Request: `database_roles: [roleB, roleC], revokeExistingRoles: true` * Result: Revokes `roleA`, Grants `roleC`. User roles become `[roleB, roleC]`. * Request: `database_roles: [roleB, roleC], revokeExistingRoles: false` * Result: Grants `roleC`. User roles become `[roleA, roleB, roleC]`. * Request: `database_roles: [], revokeExistingRoles: true` * Result: Revokes `roleA`, Revokes `roleB`. User roles become `[]`. * Request: `database_roles: [], revokeExistingRoles: false` * Result: No change. User roles remain `[roleA, roleB]`.

  Connector

• get_actor_roles

  Velvoite — EU Financial Regulatory Compliance

  Get available actor roles per regulation with obligation counts. Actor roles define WHO an obligation applies to within a specific regulation (e.g. 'credit_institution', 'significant_institution' for CRD/CRR, or 'ai_provider', 'high_risk_deployer' for AI Act). Use this to discover which roles exist before filtering obligations with get_obligations(actor_role=...). Returns roles grouped by regulation, sorted by obligation count. Each role includes a human-readable label and description. Args: regulation: Filter to a specific regulation code (e.g. 'dora', 'ai_act'). If omitted, returns roles for all regulations.

  Connector

• gcpinspect

  InsideOut (Riley)

  INSPECTION: Inspect GCP infrastructure for a deployed project ⚠️ **PREREQUISITE**: This tool requires a prior deployment ATTEMPT (successful or failed). Check convostatus for hasDeployAttempt=true before calling. Works even after failed deploys to inspect orphaned resources. Inspect deployed GCP resources after a deployment attempt. Use this tool when the user asks about the status or details of their deployed GCP infrastructure. It fetches temporary read-only credentials securely and queries the GCP API directly. RESPONSE TIERS (default is summary for token efficiency): - Summary (default): Key fields only (~500 tokens). Set detail=false, raw=false or omit both. - Detail: Full metadata for a specific resource. Set detail=true + resource filter. - Raw: Complete unprocessed API response. Set raw=true. REQUIRES: session_id from convoopen response (format: sess_v2_...). Supported services: apigateway, bastion, billing, certificatemanager, cloudarmor, cloudbuild, cloudcdn, clouddeploy, clouddns, cloudfunctions, cloudkms, cloudlogging, cloudmonitoring, cloudrun, cloudsql, compute, firestore, gcs, gke, iam, identityplatform, loadbalancer, memorystore, pubsub, secretmanager, vertexai, vpc For a specific service's actions, call with action="list-actions". METRICS: Use list-metrics to see available Cloud Monitoring metrics for any service (no credentials needed — progressive disclosure). Use get-metrics to retrieve time-series data. Optional filters JSON: {"hours":6,"period":300}. Label breakdowns: Cloud Functions (by status), Load Balancer/API Gateway (by response_code_class), Cloud CDN (by cache_result). Secret Manager get-metrics returns operational health (version count, replication, create time) — no time-series. Bastion is an alias for Compute Engine metrics (SSH connection count not available as a GCP metric). BILLING: Use service=billing to inspect GCP billing. Actions: get-billing-info (check if billing enabled, which billing account), get-budgets (list budget alerts for the project — auto-fetches billing account). Requires roles/billing.viewer IAM role. Required IAM roles: Monitoring Viewer (roles/monitoring.viewer) for metrics, Secret Manager Viewer (roles/secretmanager.viewer) for secret health, Billing Viewer (roles/billing.viewer) for billing. EXAMPLES: - gcpinspect(session_id=..., service="compute", action="list-instances") - gcpinspect(session_id=..., service="gke", action="list-clusters") - gcpinspect(session_id=..., service="cloudsql", action="get-metrics", filters="{\"hours\":6}") - gcpinspect(session_id=..., service="billing", action="get-billing-info")

  Connector

• execute_sql_readonly

  mcp

  Execute any valid read only SQL statement on a Cloud SQL instance. To support the `execute_sql_readonly` tool, a Cloud SQL instance must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For a MySQL instance, the database flag `cloudsql_iam_authentication` must be set to `on`. For a PostgreSQL instance, the database flag `cloudsql.iam_authentication` must be set to `on`. * An IAM user account or IAM service account (`CLOUD_IAM_USER` or `CLOUD_IAM_SERVICE_ACCOUNT`) is required to call the `execute_sql_readonly` tool. The tool executes the SQL statements using the privileges of the database user logged with IAM database authentication. After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. The `execute_sql_readonly` tool has the following limitations: * If a SQL statement returns a response larger than 10 MB, then the response will be truncated. * The tool has a default timeout of 30 seconds. If a query runs longer than 30 seconds, then the tool returns a `DEADLINE_EXCEEDED` error. * The tool isn't supported for SQL Server. If you receive errors similar to "IAM authentication is not enabled for the instance", then you can use the `get_instance` tool to check the value of the IAM database authentication flag for the instance. If you receive errors like "The instance doesn't allow using executeSql to access this instance", then you can use `get_instance` tool to check the `data_api_access` setting. When you receive authentication errors: 1. Check if the currently logged-in user account exists as an IAM user on the instance using the `list_users` tool. 2. If the IAM user account doesn't exist, then use the `create_user` tool to create the IAM user account for the logged-in user. 3. If the currently logged in user doesn't have the proper database user roles, then you can use `update_user` tool to grant database roles to the user. For example, `cloudsqlsuperuser` role can provide an IAM user with many required permissions. 4. Check if the currently logged in user has the correct IAM permissions assigned for the project. You can use `gcloud projects get-iam-policy [PROJECT_ID]` command to check if the user has the proper IAM roles or permissions assigned for the project. * The user must have `cloudsql.instance.login` permission to do automatic IAM database authentication. * The user must have `cloudsql.instances.executeSql` permission to execute SQL statements using the `execute_sql_readonly` tool or `executeSql` API. * Common IAM roles that contain the required permissions: Cloud SQL Instance User (`roles/cloudsql.instanceUser`) or Cloud SQL Admin (`roles/cloudsql.admin`) When receiving an `ExecuteSqlResponse`, always check the `message` and `status` fields within the response body. A successful HTTP status code doesn't guarantee full success of all SQL statements. The `message` and `status` fields will indicate if there were any partial errors or warnings during SQL statement execution.

  Connector

• gcpinspect

  InsideOut (Riley)

  INSPECTION: Inspect GCP infrastructure for a deployed project ⚠️ **PREREQUISITE**: This tool requires a prior deployment ATTEMPT (successful or failed). Check convostatus for hasDeployAttempt=true before calling. Works even after failed deploys to inspect orphaned resources. Inspect deployed GCP resources after a deployment attempt. Use this tool when the user asks about the status or details of their deployed GCP infrastructure. It fetches temporary read-only credentials securely and queries the GCP API directly. RESPONSE TIERS (default is summary for token efficiency): - Summary (default): Key fields only (~500 tokens). Set detail=false, raw=false or omit both. - Detail: Full metadata for a specific resource. Set detail=true + resource filter. - Raw: Complete unprocessed API response. Set raw=true. REQUIRES: session_id from convoopen response (format: sess_v2_...). Supported services: apigateway, bastion, billing, certificatemanager, cloudarmor, cloudbuild, cloudcdn, clouddeploy, clouddns, cloudfunctions, cloudkms, cloudlogging, cloudmonitoring, cloudrun, cloudsql, compute, firestore, gcs, gke, iam, identityplatform, loadbalancer, memorystore, pubsub, secretmanager, vertexai, vpc For a specific service's actions, call with action="list-actions". METRICS: Use list-metrics to see available Cloud Monitoring metrics for any service (no credentials needed — progressive disclosure). Use get-metrics to retrieve time-series data. Optional filters JSON: {"hours":6,"period":300}. Label breakdowns: Cloud Functions (by status), Load Balancer/API Gateway (by response_code_class), Cloud CDN (by cache_result). Secret Manager get-metrics returns operational health (version count, replication, create time) — no time-series. Bastion is an alias for Compute Engine metrics (SSH connection count not available as a GCP metric). BILLING: Use service=billing to inspect GCP billing. Actions: get-billing-info (check if billing enabled, which billing account), get-budgets (list budget alerts for the project — auto-fetches billing account). Requires roles/billing.viewer IAM role. Required IAM roles: Monitoring Viewer (roles/monitoring.viewer) for metrics, Secret Manager Viewer (roles/secretmanager.viewer) for secret health, Billing Viewer (roles/billing.viewer) for billing. EXAMPLES: - gcpinspect(session_id=..., service="compute", action="list-instances") - gcpinspect(session_id=..., service="gke", action="list-clusters") - gcpinspect(session_id=..., service="cloudsql", action="get-metrics", filters="{\"hours\":6}") - gcpinspect(session_id=..., service="billing", action="get-billing-info")

  Connector

• get_company_profile

  Velvoite — EU Financial Regulatory Compliance

  Get the calling company's regulatory posture — saved entity types, actor roles per regulation, and active conditions. The profile defines WHICH regulations and roles apply to this company. Use the actor_roles to filter obligations with get_obligations(actor_role=...). The profile is the baseline — you can extend beyond it using get_actor_roles() to discover additional roles if your analysis suggests they may be relevant. If the profile is empty (profile_complete=false), the company hasn't completed onboarding yet. Guide them to set up their profile at app.velvoite.eu/account. No parameters needed — the profile is determined by the API key. Returns: company_name: Company name jurisdictions: Active jurisdictions (always includes 'eu') profile: entity_types: List of entity type codes (e.g. ['credit_institution']) actor_roles: Dict of regulation_code -> list of role codes (e.g. {'dora': ['financial_entity'], 'ai_act': ['ai_deployer']}) conditions: Dict of regulation_code -> list of active conditions (e.g. {'dora': ['uses_ict_third_party'], 'ai_act': ['always']}) profile_complete: Whether the company has selected at least one actor role

  Connector

• get_knowledge_stats

  mcp-klever-vm

  Get summary statistics of the Klever VM knowledge base. Returns total entry count, counts broken down by context type (code_example, best_practice, security_tip, etc.), and a sample entry title for each type. Useful for understanding what knowledge is available before querying.

  Connector

• get_obligation_summary

  Velvoite — EU Financial Regulatory Compliance

  Get obligation counts grouped by regulation_code. Returns total count and per-regulation breakdown with status counts (active, upcoming, overdue, expired) plus verified and with_deadline counts. No full obligation text — just counts for a quick overview. Args: entity_type: Filter to obligations applying to this entity type (e.g. 'credit_institution', 'payment_institution'). actor_role: Comma-separated actor roles to filter by (e.g. 'financial_entity,credit_institution'). Use get_company_profile to see the company's roles, or get_actor_roles to browse all available roles.

  Connector

• parliament_search_hansard

  UK Legal Research

  Search Hansard for parliamentary debates, questions, and speeches. Returns contributions from MPs and Lords including date, party, debate title, and text (capped at 3000 chars per contribution). Useful for understanding legislative intent or political context.

  Connector

• planning_search

  UK Property Data

  Find the council planning portal URL for a postcode.

  Connector

• get_bls_sector_employment

  Stratalize Finance Intelligence

  Use when benchmarking workforce planning against sector labor market conditions, assessing industry growth trajectory for strategic planning, providing economic context for board reporting, or evaluating talent acquisition timing for a specific industry. Returns BLS payroll employment by major sector with month-over-month change, year-over-year change, and trend classification from the official establishment survey covering 650,000 US worksites — the same data the Federal Reserve uses to assess labor market conditions. Example: Healthcare sector — 8.41M employed, +47K MoM, +3.2% YoY, EXPANDING for 14 consecutive months — persistent hiring demand supports above-market compensation benchmarks. Source: Bureau of Labor Statistics Current Employment Statistics.

  Connector

• get_obligations

  Velvoite — EU Financial Regulatory Compliance

  Get regulatory obligations - specific requirements extracted from regulations. Each obligation includes the requirement text, applicable article reference, deadline, which entity types it applies to, actor roles, and current status. Results are paginated (max 50 per page). Supports keyword search via the query parameter (trigram + ILIKE matching on obligation text). Combine with regulation, entity_type, and actor_role filters for precise results. Set canonical=True to get deduplicated canonical obligations with enforcement intelligence instead. Canonical obligations return one entry per unique legal requirement per actor role, with compliance difficulty and enforcement metrics. Use get_actor_roles first to discover available actor roles per regulation. Args: entity_type: Filter by entity type code (e.g. 'credit_institution', 'payment_institution'). regulation: Filter by regulation code (e.g. 'dora', 'mica', 'aml'). status: Filter by status: 'upcoming', 'active', 'overdue', or 'expired'. query: Keyword search on obligation text (e.g. 'ICT risk', 'strong customer authentication'). actor_role: Comma-separated actor roles to filter by (e.g. 'credit_institution,significant_institution'). Use get_actor_roles to see available roles. canonical: If True, return deduplicated canonical obligations with enforcement intelligence instead of raw obligations. page: Page number (default 1). per_page: Results per page (default 20, max 50).

  Connector

• execute_sql

  mcp

  Execute any valid SQL statement, including data definition language (DDL), data control language (DCL), data query language (DQL), or data manipulation language (DML) statements, on a Cloud SQL instance. To support the `execute_sql` tool, a Cloud SQL instance must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For built_in users password_secret_version must be set. * Otherwise, for IAM users, for a MySQL instance, the database flag `cloudsql_iam_authentication` must be set to `on`. For a PostgreSQL instance, the database flag `cloudsql.iam_authentication` must be set to `on`. * After you use the `create_instance` tool to create an instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. The `execute_sql` tool has the following limitations: * If a SQL statement returns a response larger than 10 MB, then the response will be truncated. * The `execute_sql` tool has a default timeout of 30 seconds. If a query runs longer than 30 seconds, then the tool returns a `DEADLINE_EXCEEDED` error. * The `execute_sql` tool isn't supported for SQL Server. If you receive errors similar to "IAM authentication is not enabled for the instance", then you can use the `get_instance` tool to check the value of the IAM database authentication flag for the instance. If you receive errors like "The instance doesn't allow using executeSql to access this instance", then you can use `get_instance` tool to check the `data_api_access` setting. When you receive authentication errors: 1. Check if the currently logged-in user account exists as an IAM user on the instance using the `list_users` tool. 2. If the IAM user account doesn't exist, then use the `create_user` tool to create the IAM user account for the logged-in user. 3. If the currently logged in user doesn't have the proper database user roles, then you can use `update_user` tool to grant database roles to the user. For example, `cloudsqlsuperuser` role can provide an IAM user with many required permissions. 4. Check if the currently logged in user has the correct IAM permissions assigned for the project. You can use `gcloud projects get-iam-policy [PROJECT_ID]` command to check if the user has the proper IAM roles or permissions assigned for the project. * The user must have `cloudsql.instance.login` permission to do automatic IAM database authentication. * The user must have `cloudsql.instances.executeSql` permission to execute SQL statements using the `execute_sql` tool or `executeSql` API. * Common IAM roles that contain the required permissions: Cloud SQL Instance User (`roles/cloudsql.instanceUser`) or Cloud SQL Admin (`roles/cloudsql.admin`) When receiving an `ExecuteSqlResponse`, always check the `message` and `status` fields within the response body. A successful HTTP status code doesn't guarantee full success of all SQL statements. The `message` and `status` fields will indicate if there were any partial errors or warnings during SQL statement execution.

  Connector

• get_fomc_rate_probability

  Stratalize Finance Intelligence

  Use when providing monetary policy narrative context for a macro brief, investment committee, or CFO rate planning session. Returns illustrative cut, hike, and hold probabilities for the next three FOMC meetings based on current FRED fed funds data. Scenario planning tool — not futures-implied market odds. Example: Hold probability 68% at next meeting, cut probability 31% — conditioned on fed funds at 5.33% and latest CPI print. Source: FRED St. Louis Fed.

  Connector

• audit_taxonomy

  Velvoite — EU Financial Regulatory Compliance

  Audit the actor role taxonomy: compare model-defined roles vs deployed roles in the database. Returns per-regulation analysis showing: - model_only: roles the enrichment model can produce but aren't in the DB yet (gap) - deployed_only: roles in the DB but not in the model (unexpected — data quality issue) - role_counts: each deployed role with obligation count - known_issues: overlaps, naming issues, investigation items Use this for QA validation of the actor role taxonomy. Requires admin API key. No parameters needed — returns full corpus audit.

  Connector

• get_similar_jobs

  AI Dev Jobs

  Given a job ID or slug, return active jobs that match on tag overlap, same workplace, level, and job type. Ranked by similarity score (tag overlap weighted 3x). Use after search_jobs to surface nearby roles — matches the /jobs/{id}/similar REST endpoint.

  Connector

• scope.definition.create

  FreelanceOS

  Define and persist the agreed project scope with deliverables, boundaries, and exclusions. Use this tool when starting a new project or immediately after a proposal is accepted by the client to establish a clear, shared understanding of what will be built.

  Connector

• get_city_guide

  tickadoo-mcp

  Use this when the user wants an orientation overview of a city for trip planning. Returns highlights, dominant categories, price band, best-for audience hints, seasonal notes, and a short list of local advice items.

  Connector

• search_jobs

  Jobs Base

  Search and filter builder job listings on jobsbase.io — a curated board exclusively for "builder" roles (cross-functional positions where one person owns engineering, product, and delivery end-to-end: founding engineers, solo builders, 0-to-1 roles). Every job here is already an AI-native builder role, so do NOT search for generic terms like "builder", "AI", "full-stack", or "engineer" — they are redundant and will hurt results. Just use filters (country, workplace, seniority, etc.) to narrow down. Use q only for specific technologies, companies, or domain keywords. All parameters are optional.

  Connector

• get_supported_vaadin_versions

  docs-mcp

  Returns the latest stable release for each supported Vaadin major version (25, 24, 23, 14, 8, 7) with version number, release date, and whether it requires a commercial license. Useful for migration planning and understanding which versions are available.

  Connector