Skip to main content
Glama
Sign In
maviapi

maviapi

by kuzenlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Check a maviapi build

get_build_status
Read-only

Track a create_api build by request_id: returns queued, building, deploying, published, or failed so you know when it completes; published means completed, not public—check every few minutes.

Instructions

Progress of a build started with create_api: queued, building, deploying, published, or failed. The build status published means the build completed, not that the API is publicly available. Checks catalog visibility separately; the owner reviews and publishes drafts in the dashboard. Check back every few minutes rather than in a tight loop.

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": {
      "request_id": "<request_id>"
    },
    "name": "get_build_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYesThe request_id create_api returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the bar is lower, yet the description still adds real semantics: what each status value means and the non-obvious caveat that "published" does not mean the API is publicly available. It omits edge behavior for an unknown/invalid request_id and whether any status is terminal.

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?

Front-loaded with the core purpose and status set, with no filler. The middle clause ("Checks catalog visibility separately; the owner reviews and publishes drafts in the dashboard") is compressed to the point where its subject is ambiguous, which slightly hurts scanability.

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 one-parameter read tool with no output schema, the enumeration of possible statuses effectively substitutes for a return-value spec, and the polling guidance covers the main operational need. Minor gaps remain around invalid request_id handling and whether extra fields are returned.

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

Parameters3/5

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

Schema coverage is 100% and the single request_id parameter is already documented in the schema as "The request_id create_api returned," which the description merely echoes. Baseline 3 applies since the schema carries the load.

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+resource (build progress) tied to create_api, and enumerates the returned states: queued, building, deploying, published, failed. An agent can distinguish it from get_api (catalog lookup) and create_api (launch) without opening any schema.

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 a polling cadence ("check back every few minutes rather than in a tight loop") and implies it follows create_api. It also warns that catalog visibility must be checked separately, but never names the sibling that performs that check, so routing for the follow-up step is left to inference.

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

Deploy Server

Other Tools