Stackcut

Search replacement recipes

search_recipes

Read-onlyIdempotent

Use when the user wants a cheaper way to do a job and names a feature or kind of tool rather than one product: 'cheaper keyword research', 'forms without Typeform', 'what can replace our CRM'. Filter by the vendor they pay for, a feature, a category or a path type (switch, cheaper plan, open source, pay per use, agent skill, build it). Returns compact recipe cards, each with its best priced path that saves money; get_recipe has every path, cost and source. For one product they pay for, find_alternatives re-costs it at their own price and usage. Stackcut stores the arguments of tool calls to improve its recommendations (vendor names, prices, seats, features, usage numbers, billing amounts and project descriptions; account keys only as a one-way hash, billing and validation sources not at all; never IP addresses): don't send personal data or secrets.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sort`	No		relevance
`limit`	No
`query`	No	Free text, e.g. 'client approval portal' or 'semrush backlinks'
`vendor`	No	Product currently paid for, e.g. 'Airtable', 'Salesforce', 'Semrush Pro'
`feature`	No	A feature they rely on, e.g. 'rank tracking', 'e-signatures'
`category`	No	Category name from list_categories, e.g. 'CRM', 'SEO data'
`path_type`	No	Only recipes offering this kind of replacement

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 26, 2026
- addedInput schema / properties / path_type / maxLength
```
Added value: +2000
```
- addedInput schema / properties / sort / maxLength
```
Added value: +2000
```
Changed8 schema fields changedSep 26, 2026
- addedInput schema / properties / category / maxLength
```
Added value: +100
```
- addedInput schema / properties / category / minLength
```
Added value: +1
```
- addedInput schema / properties / feature / maxLength
```
Added value: +200
```
- addedInput schema / properties / feature / minLength
```
Added value: +1
```
- addedInput schema / properties / query / maxLength
```
Added value: +300
```
- changedInput schema / properties / vendor / description
```
Previous value: -"Product currently paid for, e.g. 'Airtable', 'Salesforce', 'Semrush'"New value: +"Product currently paid for, e.g. 'Airtable', 'Salesforce', 'Semrush Pro'"
```
- addedInput schema / properties / vendor / maxLength
```
Added value: +200
```
- addedInput schema / properties / vendor / minLength
```
Added value: +1
```

Changed1 schema field changedSep 25, 2026

changedInput schema / properties / path_type / enum

Previous value: -[
-  "switch",
-  "downgrade",
-  "open_source",
-  "per_use",
-  "build",
-  "bundled"
-]New value: +[
+  "switch",
+  "downgrade",
+  "open_source",
+  "per_use",
+  "agent_skill",
+  "build",
+  "bundled"
+]

First observedSep 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds a valuable disclosure that Stackcut stores call arguments for recommendations, specifies what is and isn't stored, and warns not to send personal data or secrets. This goes beyond the annotations, though it stops short of covering details like rate limits or auth.

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

Conciseness4/5

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

The description is front-loaded with the use case and examples, and every sentence contributes either routing, parameter, output, or privacy information. The privacy list is detailed but earned; it could be tightened, but it is not padding.

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?

Given no output schema, it describes the output as compact recipe cards with a best-priced path and points to get_recipe for full path/cost/source details. It covers the main input dimensions and the important privacy caveat. A minor gap is that it does not explicitly distinguish search_recipes from the closely named search_workflow_recipes, but the description is otherwise sufficient for correct invocation.

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

Parameters4/5

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

The description adds human-readable meaning to the filter parameters: vendor is 'the product they pay for', feature is the relied-on capability, and path_type is expanded into 'switch, cheaper plan, open source, pay per use, agent skill, build it'. With schema coverage at 71%, this meaningfully complements the schema, though sort and limit are left to the schema.

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

Purpose5/5

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

The description opens with a specific trigger ('wants a cheaper way to do a job') and names the resource: replacement recipes. It lists concrete filter dimensions and return type, and points out get_recipe and find_alternatives as different tools, so a selecting agent can tell it apart without reading the schema.

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

Usage Guidelines5/5

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

It explicitly says when to use this tool: when the user names a feature or kind of tool rather than one product, with example queries. It also gives routing guidance to find_alternatives for a single paid product and to get_recipe for exhaustive paths, which is a clear when-not-to-use statement.

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

All Stackcut 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.

Search replacement recipes

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources