Skip to main content
Glama

ein-llc

prepare_application

Prepare a provisional application and return the human claim URL. A human must claim and pay. This does not file, charge, or approve.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
assessmentNo
operationIdNoOptional caller idempotency key for a bound prepare. Trimmed and limited to 200 characters. When omitted, the key is prepare:{assessmentId}:{intendedEmailNormalized} and is specific to that assessment and recipient, and a missing key still recovers the application already bound to that assessment. An explicit key is not namespaced by assessment: it determines one durable application id. Reusing it for a different assessment returns 409 operation_identity_conflict. Supplying a different explicit key when this assessment is already bound returns the same 409, does not reserve that key, and returns no claim token. The same assessment with a different stored preparation returns 409 operation_payload_mismatch. Both leave the application, assessment, and authority unchanged and return no claim token. The same assessment, recipient, and stored preparation returns the original application and claim token and does not write again.
preparationNo
assessmentIdNoWhen present, the server-stored assessment is bound in one transaction with the application and authority. Same assessment plus intended email recovers the same application when the stored preparation matches. Facts and intended recipient must match the stored assessment. A different assessment cannot reuse an explicit operationId.
intendedEmailNoTrimmed/lowercased; invalid or missing email produces an incomplete application, not a claim token.
assessmentOutcomeNoFallback when preparation.assessmentOutcome is absent and no assessmentId/assessment is bound. Trimmed/truncated to 80 characters. Unknown values are refused. already_satisfied and not_needed_now are refused. insufficient_information cannot issue a claim token. Unbound allowed enum remains provisional advice, not actionable authorization.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources