Skip to main content
Glama
605,840 tools. Updated 2026-09-24 05:25

"Understanding Project Planning and Roles" matching MCP tools:

  • 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]`.
    ConnectorNo auth
  • List the teams that reach the active project and with which role. The other direction of list_team_projects — this is the tool for 'who can write here'. Requires project context. Read-only: members, roles, teams and SSO are not changeable through MCP by design — a human does those in the web app.
    ConnectorAPI key
  • PROJECT-SCOPED: this call acts only on the explicit project_id and returns the project identity with its result. Listen to bounded REAL audio through the audio-review lane and return its professional assessment. Pass asset_key for an uploaded/fetched song, audio-only file, clip or render; pass times for seconds within that asset. With no asset_key, times reviews SOURCE sound. output_times reviews the CURRENT rendered program and therefore requires render_preview first. Use this for vibe, recording quality, intelligibility, masking and mix judgment; get_audio_analysis remains the authority for BPM/beats/energy and audit_audio_mix for authored roles. Advisory only—never refuse a valid user choice because the listener is unavailable.
    ConnectorOAuth
  • List all company roles (styreleder, daglig leder, etc.) held by a person, current and historic. Use when the user asks 'what roles does Person A hold?' Pass the role_person_id returned by `search_persons`.
    ConnectorNo auth
  • List the organization's custom roles with the permission strings each one grants and how many members hold it. Use this to browse custom roles; for one role with its permissions use get_custom_role. Requires organization context. Read-only: members, roles, teams and SSO are not changeable through MCP by design — a human does those in the web app.
    ConnectorAPI key
  • Rename an existing workspace. Requires an owner or admin role in it (the same roles that may change its membership); an editor or viewer is refused. Takes the workspace id from list_workspaces. Touches only the label — membership, projects and roles are unchanged.
    Connector
    Destructive
    No auth

Matching MCP Servers

Matching MCP Connectors

  • Search Recruiter Roles: live recruiter jobs, companies, sectors, locations, and market stats.

  • Australian planning data for ~455 councils, 7 states — clause-cited, confidence-tagged.

  • CALL THIS FIRST for event staffing requests. Returns a configured-market catalog match, role-level W-2 rate math, estimated totals, tier-based lead-time guidance, and state compliance flags from the event's city, date, roles, and headcount. It does not confirm order coverage or live inventory; a coordinator does that after buyer submission. Use granular tools only for a single rate, date, or state fact. A complete plan may save a non-contact snapshot for 30 days and return plan_id plus continuation. If it returns no plan_id and the buyer needs persistence, call save_staffing_plan once; never save a plan that already has an ID. This tool never accepts or submits contact details, reserves staff, or creates a quote request. Omit roles for the catalog and a suggested mix. Treat totals as planning estimates, not quotes. Branch on status: plan, needs_roles, roles_not_found, or city_not_found; confirm suggestions rather than auto-applying them.
    ConnectorNo auth
  • Calculate IPv4 subnet details from CIDR notation. Parses a CIDR block (e.g. 192.168.1.0/24) and returns the network address, broadcast address, subnet mask, wildcard mask, first and last usable host addresses, total and usable host counts, prefix length, and classful IP class (A/B/C/D/E). Essential for homelab network planning, VLAN segmentation, firewall rule design, and understanding address space allocation. Handles special cases for /31 point-to-point links (RFC 3021) and /32 host routes.
    ConnectorNo auth
  • Score how prepared someone's end-of-life planning is and rank what is missing by consequence. Pass whichever answers are known; unanswered areas are reported back as questions to ask. Use this when someone wants to know where they stand, what to do first, or whether their planning has holes. No account needed.
    ConnectorNo auth
  • Use this when the user asks who is on their team, which teammates or seats exist, what roles are available, whether pending team invitations exist, or what team-member actions they can perform. Read-only: returns the current team roster, pending invitations, available roles, capabilities, and invitation-acceptance guidance without changing state.
    ConnectorOAuth
  • Get aggregate statistics about missions on the HomeVisto platform. Returns total counts, status breakdown, and average bounty information. Useful for understanding platform activity.
    ConnectorNo auth
  • Check subscription status, plan details, billing cycle, and feature access. Useful for understanding what the business can and cannot do on their current plan.
    ConnectorNo auth
  • List board members, daglig leder, signature holders, prokura and revisor for a Norwegian company. Set include_historic=true for people who previously held roles. Use when the user asks 'who runs X AS?' or 'who is on the board?' Roles come live from BRREG (the official enterprise register) and include role type and available appointment or resignation dates.
    ConnectorNo auth
  • Estimate what an outsourced game team costs in USD from a list of roles (discipline, seniority, headcount), an optional region and an optional duration in weeks. Returns hourly, monthly and whole-project ranges with every assumption listed. Use for "what would X cost" and budgeting questions. These are this site's editorial market ranges by discipline and seniority, not quotes from any listed studio — present them as a budget range, never as a price.
    ConnectorNo auth
  • WHEN: mapping the technical D365 objects behind a business process, or understanding which tables/forms implement a flow. Triggers: 'processus métier', 'Order-to-Cash', 'Procure-to-Pay', 'Record-to-Report', 'business process flow', 'qui est impliqué dans', 'map the process', 'flux du processus', 'quels objets dans le flux'. Map a D365 F&O business process to its complete object chain. For known processes (Order-to-Cash, Procure-to-Pay, Record-to-Report, Plan-to-Produce, Inventory-Management, Hire-to-Retire, Project-Accounting, Asset-Lifecycle): shows every step with forms, tables, classes, entities, reports, and security roles involved. For any other object name: traces all dependencies (tables, classes, forms, entities) from that entry point. Produces a Mermaid process flow diagram. Use 'list' to see all known process mappings. NOT for a single object's FK relations only -- use `find_related_objects` for that (faster and more precise).
    ConnectorNo auth
  • Decomposes a request into planned specialist roles and returns a preview; it runs no agents. Decomposes natural language requests into planned subtasks and returns a preview with specialist roles. STRICT POLICY: SeaWeb does not perform bookings, reservations, or payment transactions (booking rail retired 2026-08-04). Any booking attempts are immediately refused with a booking_retired error. task: Natural language goal or query for the agent team. max_agents: Maximum number of specialist roles to plan (default 4, range 1-5).
    ConnectorNo auth
  • List the position roster (instruments, roles) for an organization. Each row includes is_active. Defaults to active positions only so deactivated roles (Guitar, Bass, etc.) are not offered for staffing. Pass active_only=false to include deactivated roles. organization_id defaults to your active organization.
    ConnectorOAuth
  • Rename, reorder, re-rate, deactivate (is_active=false), or reactivate (is_active=true) an organization position. position_id is the org position id from list_org_positions (pass active_only=false to see deactivated roles). Name/section edits apply to custom roles only; catalog roles keep their catalog name. Deactivated roles stop being offered for staffing but keep their history. Requires org admin. Nobody is notified.
    ConnectorOAuth
  • Where an engagement stands: what is blocking it, what you owe and by when, the decisions in force and why, what the client has asked for, and what was already tried and dropped. Call it FIRST, before planning or changing anything — it is the cheapest way to avoid re-deciding something settled or contradicting a call you were not on. Called with no project, it lists the ones this user has.
    ConnectorAPI key