Skip to main content
Glama

run_slop

Execute SLOP scripts that orchestrate multiple MCP tools using inline code or file paths. Chain tool calls, loop over data, and transform results.

Instructions

Execute SLOP script with access to all registered MCPs. Inline script or file path. Returns final expression value as text.

Call MCP tools as mcp_name.tool_name(param: value). Example patterns:

Chain results between tools: data = api.fetch(id: 42) summary = ai.summarize(text: data["content"]) emit(summary)

Loop and collect: results = [] for id in [1, 2, 3]: results = results + [api.get(id: id)] emit(items: results, count: len(results))

Transform with builtins: repos = github.search(query: "mcp") names = map(repos, |r| r["name"]) emit(join(names, "\n"))

Pipe for chaining transforms (left value becomes first arg): [1, 2, 3, 4, 5] | filter(|x| x > 2) | map(|x| x * 10) data | json_stringify()

Session memory persists across run_slop calls (thread-safe): store_set("key", value) prev = store_get("key")

Persistent memory survives restarts (disk-backed): mem_save("bank", "key", value, description: "what this stores") data = mem_load("bank", "key") entries = mem_list("bank") matches = mem_search("query")

Use recipe parameter: recipe: "list" to see available templates, recipe: "" to load one. Use slop_reference to browse built-in functions (map, filter, reduce, json_parse, regex_match, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scriptNoInline SLOP script
file_pathNoPath to .slop file
recipeNoEmbedded recipe: 'list' to enumerate, or recipe name to load
Behavior4/5

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

With no annotations, the description fully carries the burden. It discloses execution behavior, MCP access, memory persistence, and thread-safety. It could be more explicit about safety or authentication, but it is quite comprehensive.

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 lengthy but well-structured: purpose first, then examples organized by pattern. Every sentence adds value, but could be slightly more concise without losing clarity.

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 the complexity of the tool (scripting, MCP calls, memory), the description covers all major aspects: tool calling syntax, chaining, loops, transforms, pipe, session memory, persistent memory, and recipe usage. It lacks error handling info but is otherwise very complete.

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?

Schema coverage is 100%, and the description adds significant value by explaining script and file_path usage with detailed examples, and recipe usage. It goes beyond just parameter names.

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 clearly states it executes SLOP scripts with access to all MCPs, inline or via file path, and returns final expression value. This distinguishes it from sibling tools like slop_help or slop_reference.

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?

The description provides extensive examples and patterns (chaining, looping, transforms, memory), giving clear usage context. However, it does not explicitly state when not to use it versus alternatives like execute_tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/standardbeagle/slop-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server