Skip to main content
Glama

start_validation

Start one bounded CSV contract validation report through your Apify account after confirming purchase, and avoid duplicate starts when an operation's status is uncertain.

Instructions

PURCHASE: explicitly start one bounded CSV report using YOUR Apify account. Completed pass/findings reports costUSD0.01. Never retry an uncertain start with another ID. Inputs stored by Apify. No repair/import permission.

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

Input Schema

NameRequiredDescriptionDefault
csvTextYesAt most20000 UTF8 bytes; public profile500records/64columns
operationIdYes
contractJsonYesAt most8000 UTF8 bytes
confirmPurchaseYes

Output Schema

NameRequiredDescriptionDefault
runIdYes
stateYes
limitsYes
reportYes
billingYes
operationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare non-readOnly, non-idempotent and openWorld, and the description adds real context beyond them: the USD 0.01 cost per completed report, that inputs are stored by Apify, and that an uncertain start must be retried with the same ID rather than a new one. These are exactly the money, data-retention and retry-semantics facts an agent needs before a paid mutation; only failure/duplicate handling detail is missing.

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?

Six short clauses, front-loaded with the PURCHASE warning and cost, with no filler. Every sentence carries an operational fact (price, retry rule, data handling, permission scope).

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?

An output schema exists, so return values need no explanation, and the description covers cost, storage and retry safety for a paid four-parameter mutation. What it omits is prerequisite state and what happens on failure or on reuse of the same operationId, which matters for a tool that charges money.

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 50%: csvText and contractJson carry size/limit descriptions in the schema, while operationId and confirmPurchase have only a pattern and a const. The description indirectly clarifies confirmPurchase ('PURCHASE') and hints that operationId is an idempotency key via the retry warning, but it adds no size, format, or content guidance of its own.

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 uses a specific verb-plus-resource framing ('explicitly start one bounded CSV report') and flags it as a PURCHASE, so the agent knows this launches a paid validation job rather than a draft or read. It does not differentiate itself from the sibling start_validation_from_draft, which is presumably the closest alternative, so it stops short of a 5.

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?

It gives a concrete retry rule ('Never retry an uncertain start with another ID') and notes there is 'No repair/import permission', which constrains what the tool is for. However, there is no explicit statement of when to pick this over start_validation_from_draft or what prerequisite state (e.g., an accepted contract) is required before calling it.

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