Skip to main content
Glama

submit_encrypted_deliverable

[Private] Seller: submit the dataset you delivered. We check it for malware, prompt injection and row count, then release or refund the escrow. Example: jobId='JOB-1001'.

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": {
      "jobId": "<jobId>",
      "rawDatasetJsonString": "<rawDatasetJsonString>"
    },
    "name": "submit_encrypted_deliverable"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYesActive escrow job identifier (e.g. JOB-1001).
rawDatasetJsonStringYesSerialized JSON array of dataset rows to encrypt and audit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / jobId / description
      Added value: +"Active escrow job identifier (e.g. JOB-1001)."
    • addedInput schema / properties / rawDatasetJsonString / description
      Added value: +"Serialized JSON array of dataset rows to encrypt and audit."
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world operation; the description adds valuable context beyond that by disclosing the three audit checks (malware, prompt injection, row count) and the outcome branch (release or refund escrow). It does not address what happens on resubmission despite idempotentHint=false, which is a real gap for a submit tool.

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?

Two tight sentences with the role and action front-loaded and the consequence trailing. The trailing jobId example repeats what the schema already shows, which is the only wasted element.

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?

With only two required, fully documented parameters and no output schema, the description covers actor, action, checks, and outcome branch adequately. The missing piece is retry/resubmission semantics for a non-idempotent submission, but overall it is sufficient to call the tool correctly.

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 100%, so both jobId and rawDatasetJsonString are already documented. The description's only added detail is the example jobId='JOB-1001', which duplicates the schema's own example, so baseline 3 applies.

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 gives a specific verb and resource (submit the delivered dataset) plus the actor ('Seller'), which separates it from the audit_* siblings that evaluate escrows rather than accept a submission. It stops short of explicitly naming a competing tool an agent might pick instead, so it is clear but not maximally differentiating.

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?

'Seller: submit the dataset you delivered' establishes the role and the precondition that a delivery has already happened, and the mention of escrow release/refund clarifies the downstream consequence. There are no explicit when-not conditions or named alternatives, so it is clear context rather than full routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.