DPYC Oracle

Overview Schema Source Related Servers Discussions Admin

get_campaign

Retrieve a published pricing campaign by its slug, author npub, and operator npub. Select JSON for importable data or markdown for a readable summary.

Instructions

Retrieve a published pricing campaign.

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

Input Schema

Name	Required	Description	Default
`slug`	Yes	The campaign slug (directory name).
`format`	No	"json" for importable data, "markdown" for readable summary.	json
`author_npub`	Yes	The campaign author's npub.
`operator_npub`	Yes	The target operator's npub.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Sep 15, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only says 'Retrieve...' which implies a read operation, but it doesn't state what happens for missing or unpublished campaigns, whether any targeting is needed, or that the 'format' parameter changes the output shape. The 'published' qualifier adds a minor constraint but little else.

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?

One short sentence with no filler. The verb and target are front-loaded, and every word 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?

For a simple retrieval tool with a complete schema and an output schema, this is minimally viable. However, it lacks guidance about the 'format' parameter's effect, the selection criteria between get_campaign and list_campaigns, and what happens if the campaign isn't published or doesn't exist. The outpu schema covers return values, but the description is thin on operational context.

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 input schema already documents all four parameters and their meanings. The description itself adds no parameter-level detail, so it stays at the baseline 3.

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 states a specific verb ('Retrieve') and resource ('published pricing campaign'), clearly distinguishing it as a singular-item getter against siblings like list_campaigns and publish_campaign. It doesn't explicitly name or contrast those siblings, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool instead of list_campaigns, how to obtain the required npub/slug values, or any exclusions for unpublished campaigns. The word 'published' implies a constraint but the description never says 'use this over X' or 'not for unpublished.'

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