Skip to main content
Glama
Sign In

Fastero

by com.fastero
OverviewDiscussionsAdmin

Replace Streamlit app files

fastero_replace_streamlit_files
DestructiveIdempotent

Replace ALL of a Streamlit app's files with the ones sent — any file left out is deleted. It suits deploying a whole folder; fastero_write_streamlit_file changes one file. A running app picks up code changes in about 5 seconds; a changed requirements.txt applies on the next start. An app imported from Git keeps these edits across its starts until they're sent to its repository as a pull request, or discarded, from the app's workspace.

Input Schema

NameRequiredDescriptionDefault
appIdYesA Streamlit app’s id, from fastero_list_streamlit_apps.
filesYesThe app's files. Each is { name, content, path? }: name has no slashes, path is the folder inside the app ('.' — the default — for the top level). The platform always runs app.py at the top level, so include it; add requirements.txt for extra packages.
projectIdYesThe project’s id, from fastero_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / appId / description
      Added value: +"A Streamlit app’s id, from fastero_list_streamlit_apps."
    • addedInput schema / properties / projectId / description
      Added value: +"The project’s id, from fastero_list_projects."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well past the annotations: it spells out that omitted files are deleted (concretely confirming destructiveHint), that a running app reloads code in about 5 seconds while a changed requirements.txt applies on next start, and that Git-imported apps retain edits until a pull request is sent or the changes are discarded. This deployment timing and persistence context is not derivable from the structured fields.

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?

Three sentences with no filler, and the most consequential fact (omitted files are deleted) is front-loaded before the alternative and the runtime-behavior details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the full burden and does so: deletion semantics, reload/restart timing, and edit persistence for Git-imported apps are all covered, and required params are documented in the schema.

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%, so the schema already explains appId, projectId, and the files array including name/path/content rules and the app.py/requirements.txt conventions. The prose does not add parameter syntax or constraints beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('Replace ALL of a Streamlit app's files') and immediately clarifies the destructive scope ('any file left out is deleted'), which distinguishes it from the sibling fastero_write_streamlit_file that changes a single file. An agent can select it without opening 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?

Explicitly scopes the use case ('It suits deploying a whole folder') and names the alternative and its contrasting behavior ('fastero_write_streamlit_file changes one file'). The routing decision between the two tools is fully stated.

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

All Fastero toolsInspect
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.

Resources