Skip to main content
Glama
Sign In

Faable — Deploy & Auth

by com.faable
OverviewDiscussionsAdmin

Retry a failed deployment

redeploy

Rebuild a failed deployment from the source it recorded. Without deployment, the newest failed one. Refused for code older than what production serves.

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": "redeploy"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare the write/non-destructive/open-world profile, so the bar is lower. The description still adds genuine behavior: it rebuilds from a recorded source rather than arbitrary code, defaults to the newest failed deployment, and refuses stale code. It doesn't say whether a new deployment object is created or what permissions are needed.

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 short sentences, purpose front-loaded, followed by the defaulting rule and the refusal condition. Every sentence carries distinct information with no filler.

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 mutating tool with no output schema, it covers purpose, default target, and a precondition for refusal, and annotations cover the safety profile. It omits what a successful call returns or creates and any auth requirements, which is the 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 coverage is 67% and the `deployment` parameter has no schema description at all. The description supplies its meaningful semantics ('Without `deployment`, the newest failed one'), compensating for the gap, while app/project are already documented in the schema.

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

Purpose4/5

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

States a specific verb and resource: 'Rebuild a failed deployment from the source it recorded.' An agent can distinguish this from siblings like cancel_deployment or create_app. It stops short of naming which sibling to use when, so it doesn't reach a 5.

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?

Gives clear operating context: without `deployment` it targets the newest failed one, and it is 'Refused for code older than what production serves.' This is useful when-to-use and constraint information, though it never contrasts with alternatives such as cancel_deployment.

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