Agent-Skills.md

Agent Skills: Greenspark Impact API (MCP reads)

>-

UncategorizedID: getgreenspark/mcp/greenspark-impact

Repository

getgreenspark/mcp
getgreensparkLicense: MIT

Install this agent skill to your local

pnpm dlx add-skill https://github.com/getgreenspark/mcp/tree/HEAD/skills/greenspark-impact

Skill Files

Browse the full folder contents for greenspark-impact.

Download Skill

Loading file tree…

skills/greenspark-impact/SKILL.md

Skill Metadata

Name
greenspark-impact
Description
>-

Greenspark Impact API (MCP reads)

Related skills

Apply greenspark-mcp and greenspark-auth-environments before live calls.

Ledger endpoints (MCP when toggled)

| operationId | Route | |-------------|-------| | getImpactPurchases | GET /impacts/purchases | | getImpactPurchase | GET /impacts/purchases/:purchaseId |

Use get-endpoint for schema, then optional execute-request on GET with a sandbox key.

Impact creation (POST) is documented on ReadMe but not executable via MCP v1 — implement writes in your application and use the API docs for POST schemas.

MCP rules (v1)

  • Impact spec is MCP-enabled for GET ledger routes when toggled in ReadMe.
  • Read-only via MCP in v1.

Transparency (ledger responses)

Purchase responses include proof that impact was delivered, notably receiptUrl and an evidences array (impact-type-specific proof such as planting sessions or plastic collection details). Use get-endpoint for the full TransactionPurchase schema.

For how ledger fits into a full integration, see greenspark-integration-workflow.

Agent guidance

  • For ledger or purchase history: use getImpactPurchases or getImpactPurchase.
  • Prefer sandbox for exploratory reads.