Skip to main content
Glama

Update profile and onboarding

spur_update_workspace

Edit your business identity, email preferences, market/outreach intent, or dismiss/restore the checklist. Identity is used by template merge fields. Does not change credentials or account permissions.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish that this is a non-destructive write that is not idempotent, so the description does not need to restate that. It adds genuine context: identity fields feed template merge fields (a downstream consequence of edits) and credentials/permissions are out of scope. It does not mention that the action modes are mutually exclusive or that only one branch can be submitted per call.

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

Conciseness5/5

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

Three short sentences, front-loaded with the four editable areas, then a downstream consequence, then a scope exclusion. Nothing extraneous or repeated from the schema.

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 four-branch polymorphic update tool with no output schema, the description accounts for all modes, notes the merge-field consequence, and carves out credential/permission scope. It is close to complete; the main gap is that it does not say whether one call handles one mode only, which matters for this oneOf shape.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents every field and the action const values; this sets the baseline at 3. The description groups the action values into four recognizable categories, which gives light semantic framing, but adds no field-level meaning beyond the schema.

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

Purpose4/5

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

The description names a specific verb (Edit) and enumerates the four distinct resource areas it mutates: business identity, email preferences, market/outreach intent, and checklist dismissal/restoration. These map directly onto the schema's oneOf branches, so an agent can tell which mode it would be invoking. It stops short of explicitly distinguishing itself by name from close siblings like spur_update_personalization_settings.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the enumeration of editable areas suggests which action to pick, and 'Does not change credentials or account permissions' provides one exclusion. There is no explicit when-to-use guidance versus the nearest alternative (personalization settings), so an agent must infer the boundary.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources