Skip to main content
Glama

ai_modeling_refine_submit

Submit a human refinement request for a Studio project using a stable request_id; submission does not guarantee delivery or automatic payment, and unknown outcomes require manual review.

Instructions

submit a human refinement request; receipt is not delivery, and payment is not automatic. Uses your Studio account and a stable request_id. Reuse returns the original job; changed input conflicts; outcome_unknown must never be blindly retried.

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>",
      "parameters": "<parameters>"
    },
    "name": "ai_modeling_refine_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
parametersYes
request_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.9/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: submission is not fulfillment, payment is not automatic, the call is bound to the Studio account, and reusing a request_id is idempotent while changed input conflicts. These idempotency and async-outcome traits are exactly what the openWorldHint/readOnlyHint=false annotations cannot convey.

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?

Dense but front-loaded: purpose first, then the receipt/payment caveat, then the request_id contract, then the retry rule. Every clause carries operational meaning; the semicolon-chained phrasing is slightly terse but not wasteful.

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 mutating, open-world submission tool with no output schema, the description covers the highest-risk behaviors: account binding, non-automatic payment, idempotency, and unsafe retries. It is thinner on what the submitted job returns and what 'outcome_unknown' looks like in practice, but the essentials are present.

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 0% and there is a nested object, so the description must compensate. It does give valuable semantics for request_id (idempotency key, reuse vs conflict), but says nothing about project_id or requirement, leaving two of three nested fields opaque.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('submit a human refinement request'), which clearly distinguishes this from siblings like ai_modeling_refine_allowance or refine_history. It does not explicitly name those siblings as alternatives, so it falls short of the 5 bar, but the purpose is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a real usage rule for the failure path ('outcome_unknown must never be blindly retried') and warns that a receipt is not delivery, which shapes how an agent should poll or wait. It never says when to choose this over the allowance/history siblings or what prerequisites (allowance check, auth) should precede it, so guidance is implied rather than explicit.

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