Skip to main content
Glama

export_accepted_contract

Read-onlyIdempotent

Exports canonical contract JSON only after explicit buyer acceptance, enabling agents to retrieve the accepted contract without purchase or import.

Instructions

Export canonical contractJson ONLY after explicit acceptance in this buyer state. No purchase/import. You may use it with the existing native Apify Actor through your own authorized account.

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

Input Schema

NameRequiredDescriptionDefault
draftIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already establish this as a safe, idempotent, closed-world read, so the description's main added value is the acceptance gate and the note that use requires your own authorized Apify account. However, "Export" is ambiguous about what actually happens (returned payload vs. produced artifact) and it says nothing about pagination, size limits, or failure modes when the draft is not yet accepted.

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?

The gating condition is front-loaded, which is good, but the second and third sentences ("No purchase/import" and the Apify Actor licensing sentence) are fragmentary and cryptic rather than informative. Nothing is padded, yet several sentences are unclear rather than earning their place.

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?

For a one-parameter, annotation-covered read tool this is close to adequate, and "canonical contractJson" hints at the return shape despite there being no output schema. Gaps remain: what draftId refers to, what happens if acceptance has not occurred, and what "buyer state" means for the caller's environment.

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?

There is a single parameter, draftId, with 0% schema description coverage and a hex-32 pattern that the description never mentions. The description never references draftId or ties it to the "accepted" draft, so it adds essentially no meaning beyond the bare schema.

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?

"Export canonical contractJson" gives a concrete verb and resource, and "ONLY after explicit acceptance" scopes it to an accepted draft, which separates it from accept_contract_draft and review_contract_draft. The term "contractJson" and the phrase "in this buyer state" are unexplained jargon, so the exact artifact returned is only partly clear.

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?

The definition supplies a real precondition (explicit acceptance must already have happened) and an exclusion ("No purchase/import"), which is enough context to decide when to call it. It stops short of naming the sibling that performs the acceptance step, so the agent must infer that accept_contract_draft is the prerequisite.

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