Skip to main content
Glama
Sign In
Podyx MCP

Podyx MCP

by Studio-Red-Barcelona
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

podyx_aftercare_start_amendment

Read-onlyIdempotent

Preview amendment options for a session to start an aftercare amendment, showing payment, approval, and fulfillment state without reserving slots or locking prices.

Instructions

Start amendment GET /api/v2/sessions/{id}/amendment-options. 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_start_amendment"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A4.1/5.0
Behavior5/5

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

It provides significant behavioral traits beyond the annotations, mentioning constraints like 'Current key authority and stored tenant ownership apply,' and detailing how external payment reporting works. This context is vital for correct decision-making.

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 quite dense and long, spanning several detailed sentences. While every sentence adds value, it sacrifices conciseness for comprehensive coverage of business rules and constraints.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite the tool's high complexity regarding financial processes, authority, and system states, the description covers all necessary high-level context. It successfully differentiates between preview/status checks and actual booking commitments.

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?

Since schema coverage is 0%, the description must provide context for the single 'id' parameter. It describes the purpose of the lookup (fetching amendment options for a specific session) but adds no structural semantics beyond the schema.

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 explicitly identifies the tool's function as fetching 'amendment-options' via a GET request on a session ID, which is clear. While it does not name a sibling tool, it defines the specific resource being manipulated.

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

Usage Guidelines4/5

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

It provides excellent operational context, stating it is 'Read/preview only' and clarifies that 'a quote does not reserve a slot or lock a price.' This sets precise boundaries on how an agent should use the tool.

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