Skip to main content
Glama
WebCake Storefront MCP

WebCake Storefront MCP

by vuluu2k

invoke_tool

Run any WebCake tool by exact name with validated arguments; discover tool names and schemas via search_tools, and use the read-only option for read-only operations.

Instructions

Run any WebCake tool by exact name with its arguments (discover names + schemas via search_tools). Arguments are validated before running. For read-only tools prefer invoke_read_tool.

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": {
      "name": "<name>"
    },
    "name": "invoke_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesExact tool name (from search_tools)
argumentsNoArguments object matching the tool's input schema

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.31.8

TDQS

A3.8/5.0
Behavior3/5

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

With readOnlyHint=false already declaring this is a non-read-only operation, the description adds useful context: arguments are validated before running, and the name must come from search_tools. However, it says nothing about failure behavior, error reporting, confirmation requirements for destructive invocations, or what the response contains — for a generic dispatcher with no output schema, those gaps matter.

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?

Two sentences, zero waste, with the core action and the prerequisite for discovery front-loaded ahead of the alternative-tool hint.

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 generic dispatcher, it covers the essentials: how to find tool names/schemas, that validation occurs, and which sibling to prefer for reads. It is slightly thin on error/return behavior given there is no output schema, but nothing critical to correct invocation is missing.

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% and both parameters are documented in-schema, including the nested 'arguments' object. The description's 'exact name' and 'its arguments' restate the schema rather than adding format or edge-case detail (e.g., how nested/unknown argument keys are handled). Baseline 3 applies.

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?

States a specific verb ('Run') and resource ('any WebCake tool by exact name with its arguments'), which is precise for a meta-dispatcher. It partially differentiates from the sibling invoke_read_tool, though the differentiation lives in the second sentence rather than the purpose statement itself.

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 an explicit prerequisite workflow ('discover names + schemas via search_tools') and an explicit alternative for a class of tools ('For read-only tools prefer invoke_read_tool'). It does not state exclusions for other cases (e.g., whether destructive tools need confirmation first), so not a full 5.

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