Skip to main content
Glama

podyx_aftercare_guests

Read-onlyIdempotent

Retrieve session guest records to check actual payment, approval, and fulfillment states. Read-only preview; follow pagination; does not reserve slots or lock prices.

Instructions

Guests GET /api/v2/sessions/{id}/guests. 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_guests"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

C2.6/5.0
Behavior3/5

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

The annotations already establish readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds some behavioral context such as tenant/key authority, pagination requirements, and read/preview-only semantics, but much of the remaining text is vague or unrelated to fetching guests.

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

Conciseness2/5

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

The endpoint is stated first, but the description is cluttered with policy statements about acceptance, provider instructions, quotes, and external money that do not clearly help an agent call this guests endpoint. Relevant pagination guidance is buried near the end.

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

Completeness2/5

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

This is a simple read-only GET with one parameter and no output schema, yet the description does not explain what guest information is returned. It includes tangential policy language instead of completing the essential picture for calling and interpreting the guests listing.

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?

Schema description coverage is 0%, so the description must carry the burden for the single nested path.id parameter. The endpoint text does imply that path.id is the session UUID, which adds useful meaning beyond the schema, but it gives no further parameter-level detail.

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 exposes the endpoint and resource: GET /api/v2/sessions/{id}/guests. That makes the basic purpose inferable as retrieving guests for a session, but it is not stated cleanly as a verb+resource action, and surrounding policy text obscures the core purpose.

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?

There is no explicit guidance on when to use this tool, when not to use it, or which sibling tools to use instead. 'Read/preview only' and 'Follow all pagination' are behavioral constraints, not usage guidance.

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