Skip to main content
Glama

PartForge

by ai.partforge
OverviewDiscussionsAdmin

Publish a forge

publish_forge
Destructive

Make a forge public at its own partforge.ai page, replacing whatever visitors currently see there. Two steps: call it with only forgeId first — nothing is published; it describes what would change and returns a confirmToken. Show the user that description and ask them to confirm. Only after they have, call it again with the confirmToken (valid 10 minutes, and only while the forge is unchanged). Never send a confirmToken the user has not explicitly agreed to in this conversation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forgeIdYesThe forge's id or its slug, exactly as list_forges or get_forge returned it.
confirmTokenNoThe token the preview call returned. Omit it to preview; send it to publish, after the user confirmed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirmToken
      Added value: +{
+  "description": "The token the preview call returned. Omit it to preview; send it to publish, after the user confirmed.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the destructive/openWorld annotations, it discloses the preview-then-commit mechanics, the token lifetime (10 minutes), the invalidation condition (only while the forge is unchanged), and the concrete scope of destruction (replacing existing public content). The conditional-token behavior is the kind of trait annotations cannot express.

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?

Front-loaded with the outcome, then the ordered steps, ending with the safety constraint. Five sentences, each carrying distinct operational information; nothing is redundant with the schema or annotations.

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?

There is no output schema, but the description compensates by describing what the preview returns (a description of what would change and a confirmToken). Combined with the explicit flow, an agent has everything needed to execute both calls correctly.

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 100%, so the schema already documents both fields; the description nonetheless adds real semantics — that omitting confirmToken yields a preview plus a token, and that the token expires and is invalidated by forge changes. It lightly augments rather than merely repeats 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?

States a specific verb and resource — make a forge public at its partforge.ai page — and immediately frames the effect as replacing what visitors currently see. This clearly distinguishes it from the sibling make_forge_private without needing to open either 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 prescribes the two-step protocol: call with only forgeId to preview, show the user, get confirmation, then call again with confirmToken. It also states a hard prohibition ('Never send a confirmToken the user has not explicitly agreed to in this conversation'), which is exactly the when-not-to guidance an agent needs.

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

All PartForge 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