Grant another user access to a BeezUP store by sharing it through the Merchant API.
Share a store to another user
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "ShareStore"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| body | No | Request body |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided. The description does not disclose behavioral traits such as side effects, reversibility, notifications, or permissions required. For a mutation operation, this is insufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, but too terse. It is concise but omits critical details. Every sentence should earn its place; here it does not provide enough information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
No output schema, no annotations, and a single parameter with a vague description. The tool is incomplete for an agent to use correctly—needs details on input structure and response.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The only parameter 'body' is described as 'Request body' in the schema, which adds no meaning. The description fails to specify what fields the body should contain (e.g., storeId, userId). Schema coverage is 100% but the provided description is trivial.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Share a store to another user' gives a verb+resource, but is vague. It does not specify what sharing means (e.g., granting access, sending a request). Compared to siblings like 'DeleteStoreShare', it implies a share entity, but without further context an agent might not know the exact action.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use vs alternatives like 'GetStoreShares' or 'DeleteStoreShare'. No prerequisites (e.g., ownership, target user existence) are mentioned, leaving the agent uncertain about proper invocation context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.