Podyx MCP

podyx_aftercare_amendment

Read-onlyIdempotent

Retrieves an amendment by ID for read-only review of payment, approval, fulfillment status, and frozen target or selection details.

Instructions

Amendment GET /api/v2/amendments/{id}. Current key authority and stored tenant ownership apply. Customer policies differ from explicit staff actions. Acceptance freezes the target and selection; GET states actual payment, approval and fulfillment. Provider instructions are fetched separately after preparation; external money is reported by the studio. Read/preview only. Follow all pagination; a quote does not reserve a slot or lock a price.

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": {
      "path": "<path>"
    },
    "name": "podyx_aftercare_amendment"
  }
}

Input Schema

Name	Required	Description	Default
`path`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 7, 2026

TDQS

C2.9/5.0

Behavior4/5

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

Beyond the read-only, idempotent annotations, the description adds tenant/key authority, target freezing on acceptance, and notes that provider instructions and external money are handled elsewhere. These details are useful behavioral context, though the phrasing is fragmented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, but the sentences are terse and loosely connected rather than front-loaded around a clear action. Some details, such as external money reporting, are useful but appear without enough framing.

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 read-only retrieval tool with no output schema, the description provides some lifecycle and return-content context but does not fully explain what amendment data is returned. The safety profile is adequately covered by annotations, but key usage and parameter details remain incomplete.

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

Parameters2/5

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

Schema description coverage is 0% for the single nested path.id parameter. The description exposes the endpoint template {id}, implying an amendment identifier, but it does not explain the UUID format, where the ID comes from, or other path semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says 'Amendment GET /api/v2/amendments/{id}' and mentions what GET states, but it never plainly states that this retrieves an amendment. It does not distinguish the tool from the sibling preview or start-amendment tools, leaving the agent to infer its role.

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?

The description says 'Read/preview only' and gives pagination advice, but it does not explain when to use this tool instead of podyx_aftercare_amendment_preview or podyx_aftercare_start_amendment. No clear usage context or exclusions are provided.

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

Deploy Server