list_methods
Returns the access methods (HTTP operations) bound to a resource -- the read methods, mutations, and lifecycle operations available. This is the tool an agent should call before writing any query, because the required WHERE parameters are inferred from the chosen read method. Pick the method whose SQL verb matches the intent and whose required parameters can be supplied, then call describe_method on it for the full contract, including the output fields.
See also:
[ MCP overview ] [ list_resources ] [ describe_method ] [ validate_select_query ]
Inputs
| Argument | Required | Description |
|---|---|---|
provider | Yes | Provider name. |
service | Yes | Service under that provider. |
resource | Yes | Resource under provider.service. |
Output
| Renderer | Shape |
|---|---|
| Table | One row per access method, including the SQL verb it maps to and the required parameters |
Gating
Allowed in every server mode. Read only.
Example
Try this prompt with any elicitation-capable MCP client with the StackQL MCP server registered:
For Google Compute instances, what methods are available
and what parameters are required?
Here's an example in Claude Desktop: