Skip to main content
Glama

start_validation_from_draft

Purchases one native Apify CSV contract validation from an explicitly accepted local draft using your Apify account; requires confirmPurchase=true and costs $0.01 per completed report.

Instructions

PURCHASE one native Apify validation using an explicitly accepted local draft and YOUR Apify account. Separate confirmPurchase=true is mandatory. Completed pass/findings reports costUSD0.01. Preserve original state and never retry unknown starts.

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": {
      "draftId": "<draftId>",
      "operationId": "<operationId>",
      "csvText": "<csvText>",
      "confirmPurchase": "<confirmPurchase>"
    },
    "name": "start_validation_from_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvTextYes
draftIdYes
operationIdYes
confirmPurchaseYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, idempotentHint=false and destructiveHint=false, so the description's job is to add economics and risk, which it does: reports cost USD 0.01, a separate confirmPurchase=true is required, and unknown starts must not be retried. The non-idempotent-plus-paid combination is exactly the trap an agent needs flagged. 'Preserve original state' stays vague about which state (local draft vs remote), which keeps this off a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the most important word, 'PURCHASE'. But it is written as clipped fragments with malformed tokens like 'costUSD0.01', and the caution about retries is tacked on without a clear connection to operationId, which slightly reduces scannability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, no annotations covering cost, and 0% schema description coverage across four required parameters, the description should be doing more. It handles the purchase/money dimension well but leaves the agent without a clear picture of what csvText supplies or how operationId protects against duplicate charges, which matters for an open-world, non-idempotent call.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden for four required parameters. It explains draftId ('explicitly accepted local draft') and confirms the confirmPurchase=true constraint, but csvText is never mentioned — it is unclear whether it is the input payload to validate — and operationId, the critical idempotency key for a non-idempotent paid call, is unexplained. Only half the parameters gain any meaning.

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?

The description states a specific verb and resource: 'PURCHASE one native Apify validation using an explicitly accepted local draft.' An agent can tell this is the paid execution path fed by a pre-accepted draft. It does not explicitly name the sibling start_validation or contrast with it, so the differentiation is inferred rather than stated.

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?

Usage is implied through preconditions: the draft must already be 'explicitly accepted', and confirmPurchase=true is mandatory. The closing caution 'never retry unknown starts' functions as a when-not-to-use rule. However, the description never states when to pick this over start_validation or what to do instead when a start's outcome is unknown, leaving the agent to infer the alternative path.

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