DPYC Oracle

Overview Schema Source Related Servers Discussions Admin

publish_campaign

Publish a pricing campaign to the DPYC community. Commits a machine-importable JSON and a Markdown summary to the campaigns directory for public access.

Instructions

Publish a pricing campaign to the DPYC community.

Commits both a machine-importable JSON file and a human-readable Markdown summary to the dpyc-community campaigns directory.

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": {
      "author_npub": "<author_npub>",
      "operator_npub": "<operator_npub>",
      "campaign_json": "<campaign_json>"
    },
    "name": "publish_campaign"
  }
}

Input Schema

Name	Required	Description
`author_npub`	Yes	The npub of the person who designed the campaign.
`campaign_json`	Yes	The full campaign export as a JSON string.
`campaign_name`	No	Optional display name. Derived from JSON if omitted.
`operator_npub`	Yes	The npub of the operator the campaign is for.
`campaign_markdown`	No	Optional pre-rendered Markdown. If omitted, the Oracle generates a basic summary from the JSON.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Sep 15, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral burden. It does disclose meaningful behavior: it commits both a machine-importable JSON file and a human-readable Markdown summary to the dpyc-community campaigns directory. However, it does not disclose whether re-publishing overwrites an existing campaign, whether the action is reversible, or what permissions are required.

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?

The description is two sentences with no filler. The primary action is front-loaded, and the second sentence adds concrete artifact and target-directory information that earns its 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?

Given the output schema and fully documented parameters, the description is close to complete for basic invocation. It still lacks side-effect semantics (overwrite behavior, idempotency) and usage prerequisites, which matter for a publishing tool with no annotations.

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 the schema already documents all five parameters. The tool description adds only the general framing that campaign_json becomes a committed JSON file and campaign_markdown becomes the Markdown summary. This is mildly helpful but not necessary for parameter understanding.

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 opens with a clear, specific verb and resource: 'Publish a pricing campaign to the DPYC community.' It then explains the exact mechanism, committing both a JSON file and a Markdown summary, which distinguishes this write operation from sibling read tools like get_campaign and list_campaigns.

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?

Usage is implied rather than explicit: an agent can infer this tool is for publishing campaigns, but the description does not state when to prefer it over alternatives, mention prerequisites, or note any exclusions. It also does not reference related workflows such as first registering an operator.

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