Loading ToolBench
GPTaria MCP server — post a project brief, respond with a prototype, and publish portfolio cases on GPTaria from Claude Code, Cursor, Claude Desktop or Windsurf.
GPTaria MCP has solid naming conventions (verb_noun pattern: list_projects, create_project, get_balance) and comprehensive descriptions (avg 180 chars, well above 10-char minimum). All 10 tools have descriptions. However, critical gaps exist: input schemas are present but many parameters lack descriptions (e.g., create_project's 'category' enum has null description; post_proposal_update's 'budget_currency' lacks guidance). Output schemas are completely undocumented, LLMs cannot predict response structure. Error handling is minimal; no recovery guidance or error categorization. Security is well-handled (API key via env var, no secrets in params). Composition is good, tools chain naturally (list_projects → create_response). Parameter constraints are present (enums for languages, categories, currencies) but inconsistently documented.
Publish a project brief via a Pro order (client accounts). Creates the project as a draft and returns a `payment.checkout_url` — the user pays by card in UAH (a Ukrainian bank card; quote prices in ₴, never EUR, and don't call it "monobank"). The fee covers auto-translation into every platform language. Write the brief in the user's OWN language — it is auto-translated and the language auto-detected. Before relying on checkout_url, offer a promo code: a valid promo_code publishes it free. A sandbox key validates without a draft or a charge.
Submit a response to a project (builder accounts). Markdown body (≥50 chars). Write in the user's OWN language — it auto-translates and the language is auto-detected. Responding needs an active access pass; if you have none it fails with need_access — call buy_service (day_pass or pass_30) then retry. Set secret:true to respond privately from v1 — it returns a checkout_url (pay by card in UAH); after payment the response is created PRIVATE. A sandbox key validates without persisting.
Check your AI-token balance and access status (FREE). Billing is token-only: one balance, spent per AI operation — no separate packs to count. ai_tokens_remaining matches Settings; can_run_ai=false means top up an ai_pack. response_access.active=false means you need a day_pass/pass_30 to respond.
Read the timeline of your OWN response on a project — comments and proposal versions, including your private secret-offer entries.
Output schemas completely undocumented. LLMs cannot predict response structure (fields, types, pagination). All tools return JSON via ok() wrapper but no schema is declared.
Parameter descriptions missing or incomplete. create_project's 'category' enum has null description. post_proposal_update's 'budget_currency' lacks guidance on when to use EUR vs USD vs UAH. LLMs cannot infer parameter semantics.
No error handling or recovery guidance. Tools throw raw API errors (e.g., '403 need_access') with no actionable next steps. LLMs cannot self-correct or know whether to retry.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 62 | 2026-07-28+ | v2 |
BUILDER: list the projects YOU responded to, with each status + flags — instead of scanning list_projects. status="brewing" is still open; offered_to_me=true → the client offered it to you (accept_project to close); i_won=true is a deal you already closed. Prices are your current offer.
List the client's clarifications on a project (updates the owner added to the brief — a logo, design wishes, a reference). Public read.
List open GPTaria projects (briefs) you can respond to.
List the responses (builder proposals) on a project so you can analyse, compare, and rank them. Prices shown are the current offer. Reads are live for both key types.
The GPTaria shop price list (FREE) — every service with its price in UAH (₴; paid by a Ukrainian bank card, the only currency — no EUR), what it does, how to buy it, tokens per AI pack and days per pass. Use it to quote and compare plans (Day Pass vs the better-value 30-day Pass, Super Expert). Always quote prices in ₴.
Post an updated offer (Markdown body + optional new price) or a plain comment in your OWN response thread. Append-only; no access pass needed. Entries are PUBLIC by default — visible to competing builders. Set secret:true to post privately: if the response isn't already secret it returns a checkout_url (pay by card in UAH) instead of posting, and after payment the version is published private. Write in the user's own language (auto-translated/detected).
List tools lack pagination parameters (limit, offset, page_size). No documented result caps. Large result sets could exhaust context window.
Destructive operations (create_project, create_response) lack confirmation or dry-run support. Agents could accidentally publish briefs or submit responses without user approval.