Convocore

workspace_write

Destructive

Change workspace settings: name, photo and team members; form-submission notification emails on/off. AI provider keys are set on the dashboard (keys must not pass through chat). Actions: update_team_profile — change workspace name / photo / team (read the current team on the dashboard first: the list replaces the old one) | set_form_submit_emails — turn the workspace-wide "New form submitted" / rating notification emails on or off (default on); per-agent override is vg_uiEngineFormNotifyConfig.enabled Needs: formSubmitEmailsEnabled.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "workspace_write"
  }
}

Input Schema

Name	Required	Description
`mode`	No	compact (default) = light mode: long text is cut and bulky blobs are replaced by a size marker. full = complete API response.
`action`	Yes
`usersPerms`	No	Per-member role and permissions: [{ email, role: admin\|member, permissions[] }].
`workspaceName`	No
`workspaceEmails`	No	Team member emails (the full list — omitted members lose access).
`workspacePhotoURL`	No
`formSubmitEmailsEnabled`	No	For set_form_submit_emails: false silences every "New form submitted" / rating email for all agents in the workspace. Default (unset) is on.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 29, 2026

TDQS

A4.2/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already flag destructiveHint=true and idempotentHint=false; the description adds the concrete reason – the team list is replaced wholesale and omitted members lose access – plus the default-on behavior for notification emails and the constraint that API keys must not pass through chat. It stops short of describing what a successful response returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the action list is crammed into two pipe-delimited clauses and ends with a dangling fragment ('Needs: formSubmitEmailsEnabled.'), and the internal config key vg_uiEngineFormNotifyConfig.enabled adds clutter for most callers.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation tool with no output schema, it covers the important ground: available actions, which parameters belong to which action, replacement semantics, and defaults. Only the usersPerms mapping to update_team_profile and the mode behavior are left entirely to the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 57% schema coverage, the description carries real weight: it maps workspaceName/workspacePhotoURL/workspaceEmails to update_team_profile and formSubmitEmailsEnabled to set_form_submit_emails, a mapping the schema never states. It leaves usersPerms and mode untouched, though both have schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Change workspace settings: name, photo and team members; form-submission notification emails on/off') and enumerates the two actions the tool supports. It is clearly distinguishable from workspace_read and from agent-level tools in the sibling list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives per-action guidance: update_team_profile should be preceded by reading the current team because 'the list replaces the old one', and set_form_submit_emails is scoped to workspace-wide notifications with a per-agent override. It also excludes a related task ('AI provider keys are set on the dashboard'), but never names workspace_read as the tool for reading settings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Convocore tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?