Skip to main content
Glama
Sign In

Faable — Deploy & Auth

by com.faable
OverviewDiscussionsAdmin

Configure how an app deploys

configure_repo

Change the deploy branch, the monorepo root directory ("" clears it) or the deploy mode (push: every push; ci: once CI tags a release; workflow: the repo's own GitHub workflow). Applies to the next deploy.

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

Input Schema

NameRequiredDescriptionDefault
appYesApp id (app_…), name or slug. Names are looked up in the project.
modeNo
branchNo
projectNoProject id, name or slug. Defaults to the active project (`faable project use`).
root_dirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real value beyond them: the change takes effect on the next deploy, and passing "" to root_dir clears it — both are behavioral facts an agent cannot infer otherwise.

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 tight sentences with the mutable fields front-loaded and parenthetical definitions that earn their space. No filler or restatement of the title.

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 mutation tool with no output schema and 40% schema coverage, the description covers the key fields, their semantics and the effect timing. It stops short of stating reversibility, auth requirements, or how to clear mode/branch, which is a minor remaining gap.

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 description coverage is only 40%, so the description must compensate, and it does: it explains the mode enum semantics (push vs ci vs workflow) and the empty-string clearing behavior for root_dir. It does not explain what branch does when omitted or how to unset mode/branch.

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 (Change) plus the three exact resources it mutates — deploy branch, monorepo root directory, deploy mode — and even unpacks the mode enum values. It is clearly distinguishable from siblings like link_repo or redeploy.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for altering deploy settings. No alternatives (link_repo, redeploy) are named, and there is no statement of when not to use it or what prerequisites/preconditions apply.

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

All Faable — Deploy & Auth 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