Skip to main content
Glama

Buy a projection from the agent's wallet

buy_projection

For an agent that pays from its own Machine Payments Protocol (MPP) wallet and has no fovub account: returns the payment link for one projection between two people for one seat, $1, paid with a Stripe Shared Payment Token. The paid answer starts the projection and carries its run_id; follow it with check_projection and answer_question, which need no sign-in for this run. An agent with the user's fovub sign-in uses start_projection instead. Needs no sign-in.

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": {
      "seat_id": "<seat_id>",
      "person_a": "<person_a>",
      "person_b": "<person_b>"
    },
    "name": "buy_projection"
  }
}

Input Schema

NameRequiredDescriptionDefault
seat_idYesThe seat_id that find_seat returned.
person_aYesThe first person's full name.
person_bYesThe second person's full name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive call; the description adds the missing context an agent needs: the $1 charge, Stripe Shared Payment Token payment, no sign-in requirement, and that the paid answer starts the projection and carries a run_id for follow-up calls. It does not address what happens on a duplicate or failed purchase, though the non-idempotent hint flags the risk.

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-loads the audience condition before the mechanics, so the agent can rule itself in or out immediately, and every sentence carries information (price, payment method, return value, next steps, alternative). It is dense and somewhat run-on, but no sentence is filler.

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?

Even without an output schema, the description explains what is returned (a payment link) and what the subsequent paid answer contains (run_id), and it names the two follow-up tools and their no-sign-in behavior. For a three-parameter payment tool this is sufficient to call it correctly.

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 100%, and the schema already explains seat_id (from find_seat) and the two full-name fields, so the description adds only the framing 'between two people for one seat'. No additional format, validation, or edge-case meaning is supplied beyond the schema.

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 and resource ('returns the payment link for one projection between two people for one seat') plus price and payment mechanism, and explicitly distinguishes itself from start_projection by audience (own MPP wallet, no fovub account). An agent can identify the tool without opening the schema.

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?

Gives an explicit precondition (agent pays from its own MPP wallet and has no fovub account) and names the alternative, start_projection, with the condition that selects it (agent has the user's fovub sign-in). It also tells the agent what to do after purchase: check_projection and answer_question.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources