Skip to main content
Glama

Async Demo Job

async_demo_submit

Launch a long-running solve as an asynchronous job that returns immediately, preventing multi-minute computations from blocking the MCP worker; poll status and results with separate tools.

Instructions

Reference async long-solve: launch a job that runs OFF the MCP channel and return immediately, so a multi-minute solve never blocks the worker. (This demo just computes for duration_s then returns a deterministic result; a real FEM/CFD solve plugs into the same facility — see ankusdrive/jobs.py.) Returns {job_id, status, cache_hit}; poll with job_status / job_result. A re-submit with identical (duration_s, value) is a content-hash cache hit (no recompute).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "async_demo_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueNo
workspaceNoRun this call in this named workspace
duration_sNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

The description adds substantial behavioral detail beyond the annotations: the job runs off the MCP channel, submission returns immediately, the demo computes for duration_s, and identical (duration_s, value) re-submissions hit a content-hash cache without recompute. It also states the returned fields and the polling path, which is the key operational behavior for an async submit tool.

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?

The description is front-loaded with the core purpose and async behavior, then efficiently covers demo behavior, return shape, polling, and caching. Every sentence contributes operational information, with no significant filler.

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 values, and it does: {job_id, status, cache_hit}. It also explains the follow-up polling path and caching behavior, which is enough for an agent to submit and then retrieve results correctly.

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 description coverage is only 33%, with workspace being the only parameter documented in the schema. The description explains duration_s as the compute duration and identifies (duration_s, value) as the cache key, but it does not clarify what value represents in the computation and does not mention workspace. It partially compensates for the low coverage but leaves meaningful gaps.

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 states a specific verb and resource: launch an async demo job that runs off the MCP channel and returns immediately. It also distinguishes itself from the polling siblings by naming job_status and job_result, and clarifies that this is a reference/demo implementation rather than a real solver.

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?

It clearly explains the intended context: use this to avoid blocking the worker on a multi-minute solve, then poll with job_status / job_result. It does not explicitly say when not to use it or name a synchronous alternative, but the usage context is clear enough for an agent.

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