Screwtape.ai

Publish one signed receipt as a Screwtape Verified badge

publish_receipt

Idempotent

Publish a signed receipt you own so a public page and a Screwtape Verified badge can link to that one verdict. Call it when you want to show that a specific output received a specific verdict. Do NOT call it to certify an agent in general: the page says this output received this verdict at this time, and it is not a general safety certification of the agent. Nothing is public until this call. Inputs: receipt_id (required), include_content (optional boolean, default false; true stores and shows the task and agent output only if that call was retained), label (optional, at most 80 characters), unpublish (optional boolean; true removes the public page). Returns public_url, badge_svg_url, embed_html, and embed_markdown. Requires the API key that owns the receipt. Cost: free.

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": {
      "receipt_id": "<receipt_id>"
    },
    "name": "publish_receipt"
  }
}

Input Schema

Name	Required	Description
`label`	No	Optional label, at most 80 characters.
`unpublish`	No	true removes the public page and the badge.
`receipt_id`	Yes	Receipt id from a judge or consensus response this key owns.
`include_content`	No	Default false. true copies the retained task and agent output onto the public page.

Output Schema

Name	Required	Description	Default
`embed_html`	No
`public_url`	No
`request_id`	No
`unpublished`	No
`badge_svg_url`	No
`embed_markdown`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 21, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Beyond the annotations it discloses a publication state change ('Nothing is public until this call'), the auth requirement ('Requires the API key that owns the receipt'), cost ('free'), and the removal behavior of unpublish. It also notes that include_content only exposes content 'if that call was retained', which the annotations say nothing about.

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?

The scope and the primary exclusion are front-loaded, and the 'Inputs' and 'Returns' groupings make it scannable. It runs long in a single block and repeats schema details (label length, receipt_id required) that the agent already has.

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

Completeness5/5

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

For a 4-parameter publishing mutation with an output schema, the description covers the state change, auth ownership requirement, cost, reversibility via unpublish, and the return shape. Nothing needed to call it correctly is missing.

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 100%, so the baseline is 3; the description does add the meaningful nuance that include_content only publishes content when the underlying call was retained. Otherwise it largely restates schema facts such as the 80-character label limit and the unpublish behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb ('Publish') and resource ('a signed receipt you own') with explicit scope: a public page and badge for 'that one verdict'. It preempts the most likely confusion by stating it is not a general agent safety certification, which separates it from the judge/consensus siblings that produce the receipts.

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?

It states clearly when to call ('when you want to show that a specific output received a specific verdict') and when not to ('do NOT call it to certify an agent in general'). The only gap is that no sibling tool is named as the alternative route (e.g., judge or consensus to obtain a receipt in the first place).

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

All Screwtape.ai tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?