Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Get job status

get_job
Read-onlyIdempotent

Poll a queued operation started by refine_site, add_page, add_pages, or create_visual (a finished visual comes back with the image attached, so check it before showing the user). Call every ~10s with the job_id those tools returned until status is "completed" or "failed". IMPORTANT: a "completed" job can still carry per-item failures — check the failed array and tell the user about anything in it, because one failed page never aborts the rest of the batch. Use get_site (not this tool) to poll create_site and publish_site — those run a design generation round, which is tracked separately. Creative jobs require creative:read; site build jobs require sites:read.

Input Schema

NameRequiredDescriptionDefault
job_idYesThe job ID returned by refine_site / add_page / add_pages
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark it read-only, idempotent and non-destructive, but the description adds substantial context beyond them: per-item failures persist inside a 'completed' job, the failed array must be surfaced to the user, a finished visual returns the image attached, and auth scopes differ by job type. These are exactly the behavioral traits an agent cannot infer from the structured fields.

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 purpose and the get_site exclusion are front-loaded, and every sentence carries operational value (polling cadence, failure handling, auth scopes). It is longer than average but dense rather than padded; only the parenthetical image note feels slightly tucked in.

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, so the description must explain return semantics — and it does: it names the status values, explains the failed array and the attached image for visuals, and covers auth requirements. An agent has everything needed to poll correctly and report results responsibly.

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%, so both job_id and user_goal are already documented. The description reinforces job_id provenance ('those tools returned') and frames it in the polling loop, but does not add syntax or constraints beyond the schema. Baseline 3 is appropriate when the schema carries the parameter documentation.

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 ('Poll a queued operation') and immediately names the four tools that create such jobs. It also explicitly differentiates from get_site, which handles create_site/publish_site jobs, so an agent can route correctly without opening schemas.

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?

Gives an explicit polling cadence ('every ~10s'), a termination condition ('until status is completed or failed'), and an exclusion with alternative ('Use get_site (not this tool) to poll create_site and publish_site'). This is close to ideal routing guidance.

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

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