Skip to main content
Glama

prufa_setup_workspace

Set up or read a Prufa workspace: create a free 7-day trial workspace with credits if no token exists, returning an API token shown once. Idempotent.

Instructions

Bootstrap or read the Prufa workspace this agent uses. If a token is already configured it returns the current workspace (with trial + upsell state). If NO token is set it CREATES a free 'agent_temp' workspace: no card, no charge, a 7-day trial with an included credit budget. During the trial you can run audits, monitors, discovery, and the full gremlin; after it ends monitors/discovery/gremlin_full_run are gated. The 201 response returns an api_token shown ONCE — persist it as PRUFA_API_TOKEN (or in ~/.config/prufa/mcp.json) and re-run with it set. When credits run low or the trial nears its end, tell your human to upgrade (prufa_upgrade_plan) or buy credits (prufa_buy_credits). Idempotent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional display name for the new workspace (defaults to 'agent workspace'). Ignored when a token is set.
owner_emailNoHuman owner's email — REQUIRED to create a workspace when no token is configured. Ignored when a token is set.
idempotency_keyNoOptional. Replays of the same key within 24h return the original response without re-executing — pass one to make retries safe. Omitted: a fresh key is generated, so each call executes.
Behavior5/5

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

With no annotations, the description fully discloses creation behavior, trial duration, gated features, token persistence, and idempotency. No contradictions.

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 thorough and logically structured, but slightly verbose. Every sentence serves a purpose, so still high quality.

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?

Given complexity (setup vs read, trial, credits, idempotency) and no output schema, the description covers all necessary aspects for correct agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds value by explaining that name and owner_email are ignored when token is set, and idempotency_key behavior (replays return original response).

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 the tool bootstraps or reads a Prufa workspace, with specific verb+resource. It distinguishes from siblings by focusing on workspace setup, which is unique among many sibling tools.

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?

Explicit guidance is given: when to create vs read, idempotency key for retries, and alternatives like prufa_upgrade_plan or prufa_buy_credits for post-trial actions.

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/prufa-dev/prufa-mcp'

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