AlphaWeb

business_profile_save

Save structured business onboarding memory.

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": {
      "workspace": "<workspace>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "business_profile_save"
  }
}

Input Schema

Name	Required	Description	Default
`brand`	No
`mission`	No
`business`	No
`operating`	No
`workspace`	Yes
`integrations`	No
`working_style`	No
`idempotency_key`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

C2.4/5.0

Behavior2/5

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

The annotations already state readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds no behavioral detail beyond repeating "save"—it does not explain idempotency handling, overwrite/merge semantics, workspace scoping, or what effect the write has.

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 single sentence contains no wasted words and is easy to scan. But it is under-specified rather than optimally structured, leaving no front-loaded details about the critical fields or idempotency.

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

Completeness1/5

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

This is a mutation tool with 8 parameters, nested objects, no output schema, and no parameter descriptions. The description is far too sparse to prepare an agent to call it correctly, especially regarding required fields and idempotency behavior.

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

Parameters1/5

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

The tool has 8 parameters with 0% schema description coverage, yet the description does not mention any of them—brand, mission, business, operating, integrations, working_style, workspace, or idempotency_key. An agent gets no semantic guidance for the nested objects or the required idempotency key.

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 ("Save") and resource ("structured business onboarding memory"), so an agent can tell it persists onboarding data. However, it does not distinguish this tool from nearby siblings like brand_memory_write or workspace_settings_save.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this tool versus alternatives such as brand_memory_write or workspace_settings_save. The onboarding context is only implied by the word "onboarding".

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

All AlphaWeb 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?