Skip to main content
Glama
Sign In
Spraay x402 MCP Server

Spraay x402 MCP Server

by plagtech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spraay_storage_pin

Pin data to IPFS via Pinata for permanent decentralized storage. Returns a CID for retrieval. Supports text, JSON, and base64 content with a cost of $0.005 USDC.

Instructions

Pin content to IPFS via Pinata for permanent decentralized storage. Returns CID (content identifier) for retrieval. Supports text, JSON, and base64 data. Costs $0.005 USDC.

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": {
      "data": "<data>"
    },
    "name": "spraay_storage_pin"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYesContent to pin — JSON string, plain text, or base64-encoded binary
providerNoStorage provider (default: 'ipfs')
contentTypeNoMIME type (default: 'application/octet-stream', e.g. 'application/json', 'text/plain')

Output Schema

NameRequiredDescriptionDefault
okYesTrue when the gateway call succeeded; false when it returned an error.
dataNoThe gateway response payload on success. The exact shape depends on the tool (see the tool description and the JSON in the text content block).
errorNoHuman-readable error message, present only when ok is false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations indicate write operation (readOnlyHint=false) and non-idempotent. Description adds crucial behavioral info: cost ($0.005 USDC) and permanence, which is not in annotations. No contradiction.

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?

Three sentences, no redundant information. All sentences are meaningful: action, output, supported types, cost. Perfectly concise.

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 output schema present, description adequately covers purpose, parameters, and return value. Could mention error cases or rate limits, but for a simple tool it is largely complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% of parameters. Description adds concrete examples for 'data' (text, JSON, base64), enhancing schema's generic description. Other parameters get little extra, but enough for clarity.

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 clearly states the action ('Pin content to IPFS'), the purpose ('permanent decentralized storage'), and the output ('Returns CID'). It distinguishes from siblings like spraay_storage_get and spraay_storage_status by focusing on creation of a pin.

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?

The description implies use when permanent storage is needed, but does not explicitly state when not to use it or mention alternatives like spraay_storage_status. It only mentions IPFS despite offering an arweave provider.

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

Deploy Server

Other Tools