Skip to main content
Glama

Brand Design Ltd.

by ltd.branddesign
OverviewDiscussionsAdmin

start_payment

Destructive

Start payment for a stage. Needs credentials. Without sharedPaymentToken you receive a hosted payment session, which you may complete yourself with a payment instrument issued to you, or hand to the person you act for. With a delegated shared payment token the payment settles directly. A self-registered agent must first have current DNS domain-control KYA for its HTTPS contact domain: call kya_challenge with a domain you control, publish its DNS TXT record and call kya_verify; kya_status reads the current verification. KYA does not grant buyer payment authority. On-chain payment is not accepted. Errors: OFFER_EXPIRED (409) for an advance after 30 days, FINAL_NOT_RELEASED (409) when the final payment is not open yet, PAYMENTS_DISABLED (503).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orderYesThe order id returned by create_order.
stageNoadvance: the first payment, open after accept_offer. It is 50% of the total, or the whole total when the service is paid at once (paymentPlan single in the catalogue). final: the remaining 50%, open only after the advance is paid and the seller has released the work for final payment. Defaults to advance.
secretNoRequired unless you authenticate with the Authorization header (Bearer <clientId>:<secret>, or an OAuth access token issued for this server). The secret returned by register_agent.
clientIdNoRequired unless you authenticate with the Authorization header (Bearer <clientId>:<secret>, or an OAuth access token issued for this server). The clientId returned by register_agent.
accessTokenYesThe accessToken returned by create_order.
sharedPaymentTokenNoOnly for delegated payment without a hosted page: a Stripe shared payment token granted to the seller profile in manifest.payment.networkBusinessProfile. Leave it out to receive a hosted payment session instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / accessToken / description
      Added value: +"The accessToken returned by create_order."
    • changedInput schema / properties / clientId / description
      Previous value: -"Your client identifier, if not sent in the Authorization header."New value: +"Required unless you authenticate with the Authorization header (Bearer <clientId>:<secret>, or an OAuth access token issued for this server). The clientId returned by register_agent."
    • addedInput schema / properties / order / description
      Added value: +"The order id returned by create_order."
    • changedInput schema / properties / secret / description
      Previous value: -"Your secret, if not sent in the Authorization header."New value: +"Required unless you authenticate with the Authorization header (Bearer <clientId>:<secret>, or an OAuth access token issued for this server). The secret returned by register_agent."
    • changedInput schema / properties / sharedPaymentToken / description
      Previous value: -"Optional. A Stripe shared payment token granted to the seller profile named in the manifest."New value: +"Only for delegated payment without a hosted page: a Stripe shared payment token granted to the seller profile in manifest.payment.networkBusinessProfile. Leave it out to receive a hosted payment session instead."
    • changedInput schema / properties / stage / description
      Previous value: -"Defaults to advance."New value: +"advance: the first payment, open after accept_offer. It is 50% of the total, or the whole total when the service is paid at once (paymentPlan single in the catalogue). final: the remaining 50%, open only after the advance is paid and the seller has released the work for final payment. Defaults to advance."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare destructive/non-idempotent/openWorld, and the description goes well beyond them: credential requirement, the two settlement paths, the KYA DNS precondition sequence, the on-chain rejection, and named error codes with HTTP statuses (OFFER_EXPIRED 409, FINAL_NOT_RELEASED 409, PAYMENTS_DISABLED 503). This is unusually rich behavioral disclosure.

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

Conciseness4/5

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

Front-loaded with the action, then conditions, then prerequisites, then errors — a sensible ordering. It is dense and slightly long, but nearly every clause carries operational meaning (auth, KYA sequencing, error codes) rather than filler.

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 no output schema, the description carries the return burden: it explains what a hosted session is and that a delegated token settles directly, and enumerates failure modes. It stops short of describing the concrete response payload (session handle/URL, settlement identifiers) an agent would need to continue the flow.

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 coverage is 100%, so the baseline is 3, but the description adds semantics the schema does not: the hosted-session consequence of omitting sharedPaymentToken and the delegation model behind it. It does not add timing or formatting detail for order/accessToken, hence not a 5.

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?

States a specific verb+resource (start payment for a stage) and immediately splits the behavior into two mutually exclusive modes: hosted session vs delegated token settlement. It also names the KYA prerequisite tools (kya_challenge, kya_verify, kya_status), so an agent can place it relative to siblings.

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

Usage Guidelines5/5

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

Explicitly says when each mode applies: omitted sharedPaymentToken yields a hosted session, a delegated token settles directly. It also states the precondition chain for self-registered agents (DNS domain-control KYA before payment) and the negative constraint that KYA does not grant buyer payment authority.

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

All Brand Design Ltd. toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources