Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

PayRam Helper MCP Server

REMOTE · MCP.PAYRAM.COM · 3 COMPONENTS · SCANNED AUG 3

Remote MCP server to integrate and validate self-hosted PayRam deployments.

+4 this week 70 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability78
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 3402 tokens (~63/item across 54 items; 52 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 96% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.payram.com

# add to Claude Code
claude mcp add --transport http payram-payram-helper-mcp https://mcp.payram.com/
# ~/.codex/config.toml
[mcp_servers.payram-payram-helper-mcp]
url = "https://mcp.payram.com/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "payram-payram-helper-mcp": {
      "type": "remote",
      "url": "https://mcp.payram.com/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add payram-payram-helper-mcp --url https://mcp.payram.com/ --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  payram-payram-helper-mcp:
    url: "https://mcp.payram.com/"
// mcp.json
{
  "mcpServers": {
    "payram-payram-helper-mcp": {
      "type": "http",
      "url": "https://mcp.payram.com/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 65

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://mcp.payram.com/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.payram.com CN=YR2,O=Let's Encrypt,C=US 22 Jun 2026 20 Sept 2026 RSA 2048 SHA256-RSA 56a9d28243feae2d5ded05790c6124fbb52
SANs: mcp.payram.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f
DNSSEC insecure

Validation of mcp.payram.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
payram.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.payram.com/ Verified 200
http (plaintext) http://mcp.payram.com/ HTTPS enforced 308 https://mcp.payram.com/
MCP tools — 52 exposed · ~3,136 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
assess_payram_project ~28

Inspects dependency files, frameworks, and .env status to suggest the next integration actions.

Input schema present but exposes no named parameters.

NameTypeReqDescription
detectedFilesarray
envStatusobjectyes
frameworksarrayyes
packageManagersarrayyes
payramDependenciesarrayyes
recommendedNextStepsarrayyes
summarystringyes

No examples provided.

check_node_sync ~117

Per-chain node health verdict: healthy / lagging / unreachable / listener-down. Computes how old each RPC node’s last block is — any non-BTC chain older than 10 minutes (BTC: 90 minutes, since BTC blocks every ~10m) is flagged as lagging or not syncing. Also checks the chain’s listener worker. When something is wrong it names the exact remediation (usually restart_payram_worker). Read-only — run this first; restart second; re-run this ~60s after a restart to confirm recovery.

Input schema present but exposes no named parameters.

NameTypeReqDescription
chainsarrayyes
healthybooleanyes
issuesarrayyes
workersarrayyes
workersAvailablebooleanyes

No examples provided.

check_payment_readiness ~89

Diagnoses what is NOT yet set up to accept payments, per blockchain: missing deposit wallet, chain/currency not enabled for the project, or a stopped listener worker. Read-only — reports gaps and points to the CLI for wallet setup; it does not create wallets itself.

NameTypeReqDescription
externalPlatformIdstringProject/platform ID to check currency enablement for (auto-resolved if omitted)
NameTypeReqDescription
allReadybooleanyes
chainsarrayyes
projectIdstringyes
readyChainsarrayyes

No examples provided.

create_payment_link ~146

Creates a PayRam checkout (payment) link and returns the hosted URL plus a reference_id. Authenticates with the Merchant API-Key (set PAYRAM_API_KEY). This WRITES — it creates a real payment request. The customer chooses the chain/currency on the hosted checkout. Poll status later with lookup_payment (or GET /api/v1/payment/reference/{reference_id}).

NameTypeReqDescription
amountInUSDnumberyesPayment amount in USD (must be > 0)
customerEmailstringyesCustomer email (required — the backend validates it as a non-empty email)
customerIDstringyesYour internal customer identifier (sent as customerID, required)
NameTypeReqDescription
hoststring
reference_idstringyes
urlstringyes

No examples provided.

explain_payment_flow ~19

Describe how payments move from customer initiation through settlement.

Input schema present but exposes no named parameters.

NameTypeReqDescription
descriptionstring
notesstring
sectionsarrayyes
titlestringyes

No examples provided.

explain_payram_basics ~26

Explain Payram's product pillars, architecture, payments, and payouts capabilities.

Input schema present but exposes no named parameters.

NameTypeReqDescription
descriptionstring
notesstring
sectionsarrayyes
titlestringyes

No examples provided.

explain_payram_concepts ~22

Glossary-backed explanation of Payram terminology and constraints.

Input schema present but exposes no named parameters.

NameTypeReqDescription
descriptionstring
notesstring
sectionsarrayyes
titlestringyes

No examples provided.

explain_referral_flow ~21

Detail the referrer/referee lifecycle and required APIs.

Input schema present but exposes no named parameters.

NameTypeReqDescription
descriptionstring
notesstring
sectionsarrayyes
titlestringyes

No examples provided.

explain_referrals_basics ~24

Summarize how Payram referral campaigns are configured and managed.

Input schema present but exposes no named parameters.

NameTypeReqDescription
descriptionstring
notesstring
sectionsarrayyes
titlestringyes

No examples provided.

generate_env_template ~30

Creates a .env template for configuring a merchant backend to talk to a self-hosted Payram server.

Input schema present but exposes no named parameters.

NameTypeReqDescription
descriptionstring
envExamplestringyes
notesstring
titlestringyes
variablesarrayyes

No examples provided.

generate_mock_webhook_event ~64

Generates a snippet to send mock Payram webhook events to your local endpoint for testing.

NameTypeReqDescription
languagestringyesLanguage/tool for the mock webhook request (curl for command-line testing)
statusstringyesPayment status to simulate in the mock webhook event
NameTypeReqDescription
metaobjectyes
notesstring
snippetstringyes
titlestringyes

No examples provided.

generate_payment_http_snippet ~42

Generates a raw HTTP sample for creating a Payram payment in the requested language.

NameTypeReqDescription
languagestringyesProgramming language for the HTTP payment creation snippet
NameTypeReqDescription
metaobjectyes
notesstring
snippetstringyes
titlestringyes

No examples provided.

generate_payment_route_snippet ~54

Generates a ready-to-use backend endpoint (e.g., /api/pay/create) that creates a Payram payment.

NameTypeReqDescription
frameworkstringyesWeb framework for the payment route handler (Express.js or Next.js)
NameTypeReqDescription
metaobjectyes
notesstring
snippetstringyes
titlestringyes

No examples provided.

generate_payment_sdk_snippet ~52

Generates backend code using the official Payram JS/TS SDK to create a payment.

NameTypeReqDescription
frameworkstringyesTarget framework for the SDK payment snippet. generic-http provides a framework-agnostic example.
NameTypeReqDescription
metaobjectyes
notesstring
snippetstringyes
titlestringyes

No examples provided.

generate_payment_status_snippet ~48

Generates backend code to query the status of a Payram payment.

NameTypeReqDescription
stylestringyesStyle of code snippet: sdk uses the Payram SDK, http uses raw HTTP requests
NameTypeReqDescription
metaobjectyes
notesstring
snippetstringyes
titlestringyes

No examples provided.

generate_payout_recipient_flow_snippet ~55

Generates the recommended OTP-verified payout flow: create recipient → validate OTP → create payout against the saved recipient. Use this for repeat beneficiaries; use generate_payout_sdk_snippet for one-off direct payouts.

Input schema present but exposes no named parameters.

NameTypeReqDescription
metaobjectyes
notesstring
snippetstringyes
titlestringyes

No examples provided.

generate_payout_sdk_snippet ~44

Generates a backend code snippet for creating a payout using the Payram JS/TS SDK.

NameTypeReqDescription
frameworkstringyesTarget framework for the payout SDK snippet
NameTypeReqDescription
metaobjectyes
notesstring
snippetstringyes
titlestringyes

No examples provided.

generate_payout_status_snippet ~28

Generates backend code to query the status of a payout using the Payram SDK.

Input schema present but exposes no named parameters.

NameTypeReqDescription
metaobjectyes
notesstring
snippetstringyes
titlestringyes

No examples provided.

generate_referral_route_snippet ~48

Generates a backend route such as /api/referrals/create for logging referral events.

NameTypeReqDescription
frameworkstringyesWeb framework for the referral route handler (Express.js or Next.js)
NameTypeReqDescription
metaobjectyes
notesstring
snippetstringyes
titlestringyes

No examples provided.

generate_referral_sdk_snippet ~44

Generates a backend route or service snippet to create a referral event using the Payram SDK.

NameTypeReqDescription
frameworkstringyesTarget framework for the referral SDK snippet
NameTypeReqDescription
metaobjectyes
notesstring
snippetstringyes
titlestringyes

No examples provided.

generate_referral_status_snippet ~49

Generates code to fetch referral progress, rewards, or status.

NameTypeReqDescription
stylestringyesStyle of code snippet: sdk uses the Payram SDK, backend-only shows direct API calls
NameTypeReqDescription
metaobjectyes
notesstring
snippetstringyes
titlestringyes

No examples provided.

generate_referral_validation_snippet ~25

Generates a snippet to validate referral IDs, statuses, and eligibility.

Input schema present but exposes no named parameters.

NameTypeReqDescription
metaobjectyes
notesstring
snippetstringyes
titlestringyes

No examples provided.

generate_setup_checklist ~28

Returns a step-by-step checklist of everything a merchant must configure to start using Payram.

Input schema present but exposes no named parameters.

NameTypeReqDescription
descriptionstring
itemsarrayyes
notesstring
titlestringyes

No examples provided.

generate_topup_integration_snippet ~157

For EXISTING apps: emits the recommended top-up wallet integration — ledger schema + cumulative-credit webhook handler + atomic invoice-settle function. Credits crypto payments to a user's balance first, then debits invoices from it, so over/under/late/duplicate payments become balance states, not payment exceptions. Pair with the payram-topup-wallet-integration skill. (New store with no users? Use the checkout/plugin path instead.)

NameTypeReqDescription
frameworkstringServer framework for the webhook handler + settle function.
partstringWhich piece to emit: 'schema' (ledger DDL), 'webhook' (cumulative-credit handler), 'settle' (atomic invoice debit), or 'all'.
NameTypeReqDescription
notesstringyes
snippetstringyes
titlestringyes

No examples provided.

generate_webhook_event_router ~27

Generates a backend event router that dispatches Payram webhook events to domain handlers.

Input schema present but exposes no named parameters.

NameTypeReqDescription
metaobjectyes
notesstring
snippetstringyes
titlestringyes

No examples provided.

generate_webhook_handler ~35

Generates backend code to handle Payram webhook HTTP requests.

NameTypeReqDescription
frameworkstringyesWeb framework for the webhook handler code
NameTypeReqDescription
metaobjectyes
notesstring
snippetstringyes
titlestringyes

No examples provided.

get_agent_setup_flow ~75

Returns the step-by-step setup flow for deploying PayRam as an agent. Covers install, wallet creation, faucet funding, contract deployment, and first payment. Includes chain recommendations (ETH Sepolia for testnet, Base for mainnet), faucet URLs, card-to-crypto prerequisites, and status/recovery commands for interrupted sessions.

Input schema present but exposes no named parameters.

NameTypeReqDescription
descriptionstring
markdownstringyes
titlestringyes

No examples provided.

get_daily_volume ~83

Returns the total payment volume for a given date, with breakdowns by network and currency. Only counts FILLED (completed) payments. Defaults to today if no date is specified.

NameTypeReqDescription
datestringDate in YYYY-MM-DD format. Defaults to today (UTC).
externalPlatformIdstringOptional. Auto-discovered from your account if omitted.
NameTypeReqDescription
byCurrencyarrayyes
byNetworkarrayyes
datestringyes
totalPaymentsnumberyes
totalVolumeUSDnumberyes

No examples provided.

get_payment_summary ~50

Returns payment counts: total, open, closed, and cancelled. Useful for a quick overview of payment activity.

NameTypeReqDescription
externalPlatformIdstringOptional. Auto-discovered from your account if omitted.
NameTypeReqDescription
cancelledCountnumberyes
closedCountnumberyes
openCountnumberyes
totalCountnumberyes

No examples provided.

get_payram_doc_by_id ~40

Returns the markdown for a Payram doc given its id, e.g. "features/payouts".

NameTypeReqDescription
idstringyes
NameTypeReqDescription
idstringyes
markdownstringyes
pathstringyes
urlstring

No examples provided.

get_payram_links ~20

Surface official documentation, website, and community links.

Input schema present but exposes no named parameters.

NameTypeReqDescription
descriptionstring
notesstring
sectionsarrayyes
titlestringyes

No examples provided.

get_referral_dashboard_guide ~23

Explain how to embed and manage the referral dashboard experience.

Input schema present but exposes no named parameters.

NameTypeReqDescription
descriptionstring
notesstring
sectionsarrayyes
titlestringyes

No examples provided.

get_unswept_balances ~108

Returns unswept (unsettled) balances across all wallets, broken down by blockchain and currency. Shows sweep readiness per entry (sweep, sweep_in_progress, sweep_not_allowed, no_balance) AND why stuck funds are stuck: lastSweepError (e.g. HOT_WALLET_LOW_GAS with the hot-wallet address to fund), pending SCW deployment, or missing cold wallet. Use this to answer "where is my money / why has it not swept".

Input schema present but exposes no named parameters.

NameTypeReqDescription
balancesarrayyes
totalWalletsnumberyes

No examples provided.

list_currencies ~64

Lists every blockchain currency PayRam supports on this node (chain code, network, currency code). Public endpoint — works with only PAYRAM_BASE_URL set, no API key or JWT required. Use this to discover valid blockchainCode/currencyCode values before creating payments or payouts.

Input schema present but exposes no named parameters.

NameTypeReqDescription
countnumberyes
currenciesarrayyes

No examples provided.

list_payram_docs ~44

Lists the available Payram doc ids relative to docs/payram-docs-live. Optionally scope by a prefix such as "features".

NameTypeReqDescription
prefixstring
NameTypeReqDescription
countnumberyes
docsarrayyes
prefixstring

No examples provided.

list_platforms ~38

Lists all external platforms (projects) for the authenticated user. Use this to discover your platform ID, which other tools auto-resolve if omitted.

Input schema present but exposes no named parameters.

NameTypeReqDescription
countnumberyes
platformsarrayyes

No examples provided.

list_recipients ~55

Lists saved withdrawal recipients (payout beneficiaries). Use this to find a recipient ID for the 3-step payout flow, or to check whether a beneficiary is already OTP-verified (status "active") before creating a payout.

Input schema present but exposes no named parameters.

NameTypeReqDescription
countnumberyes
recipientsarrayyes

No examples provided.

lookup_payment ~94

Look up payments by transaction hash, email, reference ID, customer ID, or invoice ID. Returns up to 5 matching payments with full details.

NameTypeReqDescription
externalPlatformIdstringOptional. Auto-discovered from your account if omitted.
querystringyesSearch query: transaction hash, email address, reference ID (UUID), customer ID, or invoice ID. The backend auto-detects the query type.
NameTypeReqDescription
paymentsarrayyes
totalCountnumberyes

No examples provided.

onboard_agent_setup ~28

Returns the complete autonomous agent setup guide for deploying Payram without any web UI or human interaction.

Input schema present but exposes no named parameters.

NameTypeReqDescription
descriptionstring
markdownstringyes
titlestringyes

No examples provided.

payram_doctor ~134

Staged, read-only health diagnosis: server reachability -> merchant API key -> admin JWT -> payment readiness (wallets + listener workers). Returns ranked likely causes with exact fix commands for the first failing stage. Run this FIRST when anything PayRam-related fails.

NameTypeReqDescription
apiKeystringMerchant API key (per-project). Defaults to PAYRAM_API_KEY. Obtain headlessly: ./setup_payram_agents.sh ensure-api-key
baseUrlstringPayRam server base URL. Defaults to PAYRAM_BASE_URL. The installer publishes on port 80 (http://localhost), not :8080.
NameTypeReqDescription
failedStageyesFirst failing stage: reachability | api-key | jwt | readiness; null when healthy
findingsarrayyes
healthybooleanyes
likelyCausesarrayyesRanked causes for the first failing stage
nextStepsarrayyes

No examples provided.

prepare_payram_test ~23

Confirm hosting, credentials, and environment variables before generating demo apps.

Input schema present but exposes no named parameters.

NameTypeReqDescription
descriptionstring
notesstring
sectionsarrayyes
titlestringyes

No examples provided.

restart_payram_worker ~169

REMEDIATION ACTION (write): restarts a blockchain listener worker via supervisor — the minimal fix when check_node_sync reports a chain as lagging or listener-down. Workflow: run check_node_sync first → restart the named worker → wait ~60s → run check_node_sync again to confirm recovery. A restart does NOT fix an unreachable RPC (fix the RPC config in the dashboard instead). Requires admin JWT with write_system_settings.

NameTypeReqDescription
allbooleanRestart ALL workers. Use only when multiple chains are unhealthy.
workerstringWorker to restart: a chain code ('BASE', 'ETH', 'BTC', 'TRX', 'POLYGON' → restarts that chain's listener) or a full worker name ('base-listener'). Omit when using all=true.
NameTypeReqDescription
messagestringyes
restartedstringyes

No examples provided.

scaffold_payram_app ~119

Generates a minimal full-stack app skeleton with Payram payments and payouts routes (and a simple UI) for a chosen language and framework.

NameTypeReqDescription
appNamestringName for the generated application. If not provided, defaults to payram-{framework}-starter
frameworkstringyesWeb framework to use for scaffolding the application
includeWebhooksbooleanWhether to include webhook handler code in the scaffolded application
languagestringyesProgramming language for the application (node for JavaScript/TypeScript)
NameTypeReqDescription
appNamestringyes
filesarrayyes
frameworkstringyes
instructionsstringyes
languagestringyes

No examples provided.

search_payments ~344

Search and filter payments with full control over status, network, currency, dates, webhook status, and pagination. Returns a paginated list of matching payments.

NameTypeReqDescription
createdByarrayFilter by creator type.
currencyarrayFilter by currency code (e.g. USDC, USDT, BTC, ETH, TRX, CBBTC).
dateFromstringStart date filter (ISO 8601, e.g. 2024-01-01T00:00:00Z).
dateTostringEnd date filter (ISO 8601, e.g. 2024-12-31T23:59:59Z).
externalPlatformIdstringOptional. Auto-discovered from your account if omitted.
limitintegerNumber of results per page. Defaults to 50.
networkarrayFilter by blockchain network (e.g. BTC, ETH, TRX, BASE, POLYGON).
offsetintegerPagination offset. Defaults to 0.
paymentStatusarrayFilter by payment status (FILLED = completed).
querystringFree-text search: tx hash, email, reference ID, customer ID, or invoice ID.
sortBystringSort field. Valid: created_at, updated_at, payment_status, currency, network, block_id, from_address, to_address, invoice_id, reference_id, customer_id, email, created_by.
sortDirectionstringSort direction. Defaults to DESC.
webhookStatusarrayFilter by webhook delivery status.
NameTypeReqDescription
limitnumberyes
offsetnumberyes
paymentsarrayyes
showingnumberyes
totalCountnumberyes

No examples provided.

snippet_express_payment_route ~28

Returns an Express router that posts to Payram's /api/v1/payment endpoint.

Input schema present but exposes no named parameters.

NameTypeReqDescription
metaobjectyes
notesstring
snippetstringyes
titlestringyes

No examples provided.

snippet_fastapi_payment_route ~26

Returns a FastAPI handler that calls Payram's create-payment HTTP API.

Input schema present but exposes no named parameters.

NameTypeReqDescription
metaobjectyes
notesstring
snippetstringyes
titlestringyes

No examples provided.

snippet_go_payment_handler ~28

Returns a Gin handler that proxies /api/pay/create to Payram's create-payment API.

Input schema present but exposes no named parameters.

NameTypeReqDescription
metaobjectyes
notesstring
snippetstringyes
titlestringyes

No examples provided.

snippet_laravel_payment_route ~29

Returns a Laravel controller that posts to Payram's /api/v1/payment endpoint.

Input schema present but exposes no named parameters.

NameTypeReqDescription
metaobjectyes
notesstring
snippetstringyes
titlestringyes

No examples provided.

snippet_nextjs_payment_route ~29

Returns a Next.js App Router API route that calls Payram's create-payment HTTP API.

Input schema present but exposes no named parameters.

NameTypeReqDescription
metaobjectyes
notesstring
snippetstringyes
titlestringyes

No examples provided.

snippet_spring_payment_controller ~28

Returns a Spring Boot controller that calls Payram's /api/v1/payment endpoint.

Input schema present but exposes no named parameters.

NameTypeReqDescription
metaobjectyes
notesstring
snippetstringyes
titlestringyes

No examples provided.